User Status

User status is decided by the ‘status’ of the user's email coming in from the primary source.

How is the primary source of a user decided?

• If a user is added manually on the Zluri platform, the primary source of that user will always be ‘Manual’.

• If an Admin changes a user's status, the primary source of the changed user becomes ‘Manual’.

• If we change any other user attribute (like Designation, etc.), the Manual source will not be added to the Sources list.

• For other users, the primary source is set according to the platform's directory management settings.

• By default, the first connected SSO/HRMS becomes the primary source for user status.

  

There is a provision to set multiple primary sources for user status also from the backend, but not from the UI. For this, you can reach out to the support team. Multiple primary sources work on a precedence order basis that can be defined by the customer.

Example:
A customer chooses both Google Workspace and Okta to be primary sources for user status with a precedence order of Google Workspace as 1 & Okta as 2.
In this case:

• All the users coming in from Google Workspace will have their primary source as Google Workspace.
• All users coming in from Okta but not from Google Workspace will have their primary source as Okta.
• Other users will have their primary source as the first source they get discovered from.

After the user’s primary source is decided, the status of the primary email coming in from the primary source is set as the status of the user in Zluri.

If the primary email does not come from the SSO/IDP, the status of any aliases coming in from SSO/IDP will be processed as the user status of the user.

When we select a primary source from Settings, that primary source determines user classification (Employee/External) as well as user status for all the users in the org coming from that primary source.

What can be processed from the Back End

• In case of GWS integration, a backend configuration is present in which we can set the user status as ‘Suspended’ on the basis of the archive key.

  • If archive: true → User Status: Suspended

• In the case of Okta, a backend configuration is present in which we can set the user status as Active based on the raw data status key.

  • (Provisioned, Active, etc.)

• The Manual source can be set as the highest or the lower priority.

Current Limitations (Internal)

If we change the source of a user using the “Set as Primary source” button on the Individual User page, this will get overridden in the next sync.