See how Ramp uses ConductorOne
ConductorOne

ConductorOne Docs

Matching data in ConductorOne and Okta

As a demonstration, we break down how the User Identity Counts match up between ConductorOne and Okta.

Example user counts in ConductorOne and Okta

ConductorOne Okta identities count

Okta People dashboard

User identity count comparison and explanation

User Title Okta ConductorOne Explanation

Everyone

[User + Service Accounts]

6 6 [(User + Service Account) - Okta Deactivated Users] Okta includes Deactivated users under Everyone, but ConductorOne will not.
Enabled 5 5 [Okta Active Users + Staged + Pending User Action] ConductorOne: [User + Service Accounts] - [Suspended/Disabled + Deactivated]
Disabled [Suspended] 1 1
Recovery [*Password Reset] 2 2

*if a user is otherwise active but in Password Reset they will show as “Recovery."

*If Password Reset is showing in Okta and Recovery is not showing in ConductorOne, the Password Reset number is rolled in the Suspended category.

*Active

[Okta double counts some statuses see “Explanation Column”]

4 2 [excludes Recovery/Resets] *Okta double-counts Password Expired, Recovery/Reset, Locked Out Users.
*Password Expired N/A N/A

If the value is zero, this field will not show in ConductorOne or Okta.

*If Password Expired is showing in ConductorOne but not Okta, it is counted under Active in Okta.

Provisioned [Pending User Action] 1 1
Suspended 1 1
Staged 0 N/A If the value is greater than zero, it will appear in ConductorOne and match Okta exactly.
Locked 0 N/A If the value is greater than zero, it will appear in ConductorOne and match exactly to Okta.