User Account Type

Zluri offers options to categorise accounts into Employee, Group, Service, and External account types.
Configurations available in the UI allow automatic classification of users into these account types.

• Employee / External categorisation is based on the selected Integration, selected Domains, or both.

• Group and Service accounts can be categorised from the platform with certain conditions (listed below).

• Automated configurations for Group and Service accounts can also be set by contacting Zluri Support.

  

What can be processed from the Back End

• From the UI, only one primary source can be selected, but from the backend, multiple primary sources can be set.
• Different sources can be used for User Status and User Classification.
• Employee vs. External classification can be based on specific strings in the email address (e.g., .ctr, #ext).
• Group and Service account classification can happen on any field from raw data, integration data, or group membership.
• Only one kind of setting per integration is supported (not multiple or a combination of raw data keys and group memberships).
• Multiple integrations are supported for classification, with processing determined by priority and availability.

Example:
If Google Workspace (GWS) and Azure are both set as primary sources, with GWS priority = 1 and Azure priority = 2:

• Users from both GWS and Azure → Primary source = GWS.

• Users from GWS only → Processed from GWS.

• Users from Azure only → Processed from Azure.

• From the backend, if a user does not exist in any of the selected primary sources, the user can be marked as Inactive.

• Employee vs. External classification always depends on backend/UI (Settings page) configurations.

• Any manual changes are overwritten in the next sync unless the user’s primary source is Manual.

  • Manual source is added only when:
    • The user is added manually,
    • The user is invited by admin, or
    • The user’s status is changed manually.

• Group/Service can be classified from the UI only if:

  • No backend configuration has been set for Group/Service classification, and
  • Employee/External classification is based on email domains only (not integration source).

• Users with the primary source Manual are excluded from backend overrides.

• If the User Account Type is manually set to Employee in the UI:

  • It is overridden on the next sync unless the primary source is Manual.

• If the User Account Type is manually set to Service/Group in the UI:

  • It is overridden if:

    • A backend configuration exists for Service/Group classification, or

    • No backend configuration exists, but Employee/External classification is based on integration source (not domains).