Skip to main content
You can connect Omni to Okta to manage authentication and user access through your organization’s existing identity provider. Okta supports SAML for single sign-on and SCIM for automated user provisioning. You can also sync additional user attributes like name, title, or department to keep Omni profiles up to date.

Integration overview

Connecting Okta to Omni allows you to:
  1. Authenticate users through Okta using SAML.
  2. Provision and deprovision users automatically with SCIM.
  3. Sync user profile data such as display name and department through attribute mappings.

Supported features

Omni supports the following Okta provisioning features:
  • Push users - Users in Okta that are assigned to the Omni application in Okta are automatically added as users in Omni.
  • Update user attributes - When user attributes are updated in Okta, they will be updated in Omni.
  • Remove/deactivate users - When users are removed or deactivated in Okta, their membership to your Omni organization will be revoked.
  • Reactivate users - Reactivating a user will create a new user in Omni with a new external ID.
  • Push groups - Groups and their members in Okta can be pushed to Omni as Omni groups and group members.

Limitations

Omni does not currently support the following Okta provisioning features:
  • Sync password
  • Enhanced group push
Additionally, note that user sessions will expire after 24 hours. This is not currently configurable.

Getting started

Follow these steps to get set up. You can complete SAML only, or add SCIM and attribute sync for a fully automated experience.
StepDescriptionLink
1Set up SAML SSO to let users sign in to Omni with their Okta credentials.SAML setup →
2Enable SCIM provisioning to automatically create, update, and deactivate users in Omni.SCIM setup →
3Sync user attributes like name, title, and department between Okta and Omni.Sync attributes →

Notes & troubleshooting

  • Admin access required: You’ll need Okta admin permissions to configure SAML and SCIM.
  • Test before rollout: Try SSO with a test user before enabling it organization-wide.
  • Sync frequency: SCIM updates usually occur within a few minutes of changes in Okta.
If you run into issues, check your Okta app configuration or see Omni’s troubleshooting SSO guide.