Background
Your Source of Truth settings enable you to pull human resources information system (HRIS) data into Lumos. For example, Lumos can automatically sync employee manager data so that you can route access requests for manager approval. Lumos can auto-ingest Source of Truth data and use it across many different workflows.Editing Source of Truth settings
You can find and make changes to your Source of Truth settings on the Source of Truth settings page. You must be a Lumos Admin to view/edit your Source of Truth settings. See Lumos Roles. Modifying these settings can have a major impact on your workflows. Read on to learn more before changing anything.User Sources
Your User Sources are one of the first things you’ll set up after you create a Lumos account. They control how Lumos Users are created and updated. You can read more about User Sources here: Importing User SourcesLogin Providers
Your Login Providers control which app employees use to log in to Lumos. When employees log in to the AppStore, Lumos automatically brings them to one of the supported login providers. Usually, set this to the same app as your User Source, but it can be configured independently. They support the following options:- Identity Provider: Use single sign-on (SSO) to log in. Choose this option to log in with Okta, BambooHR, OneLogin, or JumpCloud.
- Google: Use Google Workspace accounts to log in.
- Microsoft: Use Microsoft accounts to log in.
Manager
Importing Manager data from a supported integration automates many critical workflows. You can read more about how to import and configure Manager data here: Importing Manager DataIf manager data doesn’t populate for some users, the manager field usually holds an incomplete identifier that Lumos can’t map to a specific user, such as only a first name (“adam”). The field needs to contain either the full name (first name + last name) or an email address.To fix this, change the Source Field Name in your Manager settings to a field that holds email addresses, such as
managerEmail. An email field tends to be much more reliable than the standard manager field. See Importing Manager DataTeam
The Team field provides rich context and segmentation for many Lumos workflows and reporting features based on an employee’s team or department. You can read more about how to import and configure Team data here: Importing Team DataTitle
The Title field provides rich context and segmentation for many Lumos workflows and reporting features based on an employee’s job title. You can read more about how to import and configure Title data here: Importing Title DataTroubleshooting attribute sources
Each attribute in your Source of Truth settings points at one or more app instances, each with its own Source Field Name. This includes Manager, Team, Title, Start Date, End Date and every Custom Attribute. Lumos reads the primary source first and moves on to the next if it finds nothing. If an instance stops syncing, or the field is renamed in the source app, the attribute stops filling in from it. Lumos doesn’t move the mapping for you.Attributes stopped populating after I replaced or reconnected an integration
When you replace a connector, the new connection is a separate app instance. For example, moving from ADP Workforce Now (Merge) to ADP Workforce Now (Direct API) creates a new instance. Your attributes keep pointing at the old instance, which no longer syncs, so their values stop arriving. To fix this:- Go to Settings → Source of Truth.
- For each attribute that used the old integration, click “Edit”.
- In Source App, select the new instance.
- In Source Field Name, select the field from the new instance. Field names can differ between connectors for the same app, so don’t assume the old name still applies.
- Click “Save”.
- At the top of the Source of Truth page, click the sync icon next to Last Successful Sync to sync your user sources.
The Source App dropdown shows two apps with the same name
The dropdown lists every connected instance of an app, so an old and a new connection can share the same display name. Each entry shows the app name followed by that instance’s identifier, such as App name | instance identifier. The list can be long, so scroll through the whole dropdown before picking one. To find the right instance, open Integrations and compare the connected cards. Pick the instance that is actively syncing. An instance that hasn’t synced recently won’t update the attribute.Values stopped arriving after I renamed fields in my source app
Lumos maps each attribute by its exact Source Field Name. If you rename a field in your source app, for example a Workday field override, the attribute still points at the old name and no longer receives values. To fix this, edit each affected attribute in Settings → Source of Truth and select the new field name in Source Field Name. The values return on the next sync. The new field names appear in the dropdown after the source app syncs.An app is missing from the Source App dropdown
An app appears in the Source App dropdown only after Lumos can read the list of user fields from it. Check the following:- The integration is connected and has synced. Connect the app and wait for its first sync to finish.
- The connection can read the app’s user schema. For Okta, the admin role used for the Lumos connection needs read access to the user profile schema (
/api/v1/meta/schemas/user/default). Without that access, Lumos has no Okta fields to offer. After you grant it, the fields appear after the next sync.