User Discovery

Current Behaviour

User discovery in Zluri can happen from the following sources:

SSOs

• Azure
• Google Workspace
• Okta
• OneLogin
• JumpCloud

HRMS

• HiBob
• BambooHR
• PersonioHR
• Others

Financial Integrations

• NetSuite
• Xero
• SAP Concur
• Others

Direct Integrations

• Slack
• Jira
• JAMF
• Salesforce
• Zoom
• Others

Manual

• Bulk Add User API

Data Folders Used for User Discovery

Zluri processes user data from the following folders within integrations:

• List of Users
• Activities (for SSOs like Azure, OneLogin, and Okta — excluding Google Workspace and JumpCloud)

User Status

• The status of the discovered user is determined based on User Status.
• Users discovered from Activities are always marked as Inactive.
• If the same user is later discovered from the Users folder, their status will be updated based on the List of Users folder.

Primary Source and Email Behaviour

1. When a user is discovered for the first time, the integration where they were discovered becomes their primary source.
2. The primary email associated with the user is taken from this source.
3. Aliases, if present, are also processed from the same source.
4. If the primary source changes and the new source does not include the same primary email but does include it as an alias, the primary email ID does not change.
5. If later, the primary source of the user is changed and the new source does not have the same primary email-id but an alias of the same (processed before), then in this case the primary email-id of the user will get updated as per the primary email id coming in from the new source.