Overview
This article summarizes the different states a user can belong in Torii, how these are defined and how to customize that definition.
User States
Current Users
Current Users refer to users which Torii recognizes as active. A user is considered a “current user” if:
- They return as users for at least one application (from any discovery source).
- They return (or returned) from the IdP or HRMS applications defined as your user lifecycle source of truth as Active (or similar status). Learn more about how Torii calculates this status here.
By default, these applications are Google Workspace and Microsoft Entra ID. You can learn how to customize the user lifecycle definition for your organization here.
Past Users
Past Users refer to users which Torii recognizes as inactive. A user is considered a “past user” if:
- They return from the applications defined as your user lifecycle source of truth as Terminated (or similar status).
- They were previously found in your user lifecycle source of truth, and then stopped returning from them entirely.
Torii has an application-specific login tailored to each system to make sure we capture the correct user state. Read more about current and past user definitions for each system here.
Customizing the user lifecycle definition in Torii
To be able to differentiate between current users and past users, Torii requires information provided by at least one user lifecycle source. By default, these are set to be:
- Google Workspace (G Suite), and
- Microsoft Entra ID.
You can customize which apps are used to categorize users in the Settings -> Users & Employees page, under “User Lifecycle”. You can also read more about this here.
Past user definition per app
As a reminder, if the user returned previously from any of these sources (with any status), and later stopped returning, Torii will also consider them a past user.
|
IdP/HRMS |
Status in app aligned with past user status |
|
Azure Active Directory |
disabled |
|
Google Workspace (G Suite) |
suspended or archived |
|
JumpCloud |
Any status except active or staged
|
|
Okta |
deprovisioned (deactivated in the admin console) |
|
OneLogin |
suspended |
|
BambooHR |
terminated, and the current date is past the termination date |
|
Hibob |
terminated or garden leave |
|
Sailpoint |
terminated |
|
Namely |
inactive |
|
Workday |
inactive |
|
ADP |
Any status except active |
|
Paylocity |
terminated, and the current date is past the termination date |
| Personio |
inactive or terminated
|
| SAP SuccessFactors |
inactive |
| UKG Pro |
terminated, and the current date is past the termination date |
| Deel |
inactive |
Breakdown of user categorization logic in Torii:
Torii created the following logic to accurately determine whether a user should be considered a current or a past user.
- First, Torii relies on the currently connected user lifecycle source, and uses the user data there to determine the correct category for the user.
- If the user is not found in the relevant source, Torii checks if they were previously found there - if so, the user is considered a past user (This assumes that the user was deleted from the system due to termination).
- If the user was never seen in the relevant source, Torii checks if there’s a previous user state saved for this user. If it exists, Torii falls back to this data.
- Otherwise, Torii will put the user in the “current user” category.
Multiple lifecycle SOT systems
In the user lifecycle setting, you can configure more than one system to be your user lifecycle source of truth (SOT).
In this case, all systems must be aligned for a user to be considered a past user - A user must be considered 'past' in all relevant systems to be marked as a past user in Torii (otherwise they’ll be considered a current user).
The user's lifecycle status is determined only by systems that:
- Are currently selected as the lifecycle source of truth.
- The relevant user has been discovered in (currently or previously). Systems selected as part of the configuration in which the user was never discovered will not be taken into consideration when determining user status.
For multiple lifecycle SOTs, Torii will fall back to the previously known user status only if:
- The user does not return from any selected system.
- The user has never returned from any selected system.
FaQ
Q: In the Users page, the number of “All Users” is greater than the sum of “Current Users” and “Past Users” combined. Why is this?
A: This is because Torii excludes from the Current Users table users which return from 0 apps. This is to prevent clutter from irrelevant users found from the different discovery sources. You can still find these users in the “All Users” tab.