Importing Team Data
Last updated: October 9, 2024
Background
This article breaks down the Team field in your📄 Source of Truthincluding how and why you set it, the impact of making changes to it, and common questions or issues.
Purpose and function
The Team field helps inform many important workflows in Lumos. You'll see the Team value show up:
As a column in your Access Reviews to help reviewers understand more about the employee when making decisions.
In access requests made from the AppStore to provide useful context during approvals. See📄 Approving Access Requests
When targeting the scope of an access review to specific teams. See📄 Scoping Your Access Review
When viewing the list of user accounts discovered for an individual application.
For segmenting spend in our analytics dashboard. See📄 Understanding Your Spend with Lumos
Editing Team settings
1. Go to your Source of Truth settings.
2. Find the Team section and click "Edit".
3. Choose the Source App that holds the most accurate user data.
If the app you choose here is different from your User Sources, please contact us so we can ensure you won't run into any issues! See📄 Importing User Sources
4. In the Source Field Name, choose the name of the field that holds the team data and click "Save".
Below you can find more context around which fields are supported ("From which apps and fields can Lumos source team data?" section in this article). Make sure you choose a supported field!
FAQs
From which apps and fields can Lumos source team data?
The following apps + app fields can be used to source Team data.
Field | Source | Notes |
Google Workspace Team | This is the Google User's Organizational Unit. | |
Okta | Any Okta profile field | Â |
OneLogin | Any OneLogin profile field | Â |
BambooHR Department | Â | |
BambooHR Division | Â | |
Azure AD Department | Â | |
Workday Department |
| We check for the |
Workday Cost Center |
| We check for the |