Identity Connector for Okta

Alicia Allen Updated by Alicia Allen


With Brivo's Identity Connector, customers can provision their Okta users and groups to Brivo Access, allowing them to manage onboarding and offboarding users in a single application.

Supported Provisioning Features

  • Push New Users: Users assigned to the application in Okta will be created in Brivo Access. 
  • Push User Deactivation: Deactivating the user through Okta will deactivate the user in Brivo Access.
  • Push Profile Updates: Updates made to the user's profile in Okta will be pushed to Brivo Access.
  • Push Groups: Groups and their members can be pushed to Brivo Access from Okta.
  • Reactivate Users: Reactivating the user through Okta will reactivate the user in Brivo Access.
  • Mapping Custom Attributes: Custom Attributes in Okta can be mapped to Custom Fields created in Brivo Access.
  • Push Brivo Mobile Pass Credential: BMP credentials can be issued via Okta provisioning to the user in Brivo Access.
  • Push Brivo Wallet Pass Credential: Brivo Wallet Pass credentials can be issued via Okta provisioning to the user in Brivo Access.

Supported User Fields

  • userName
  • givenName
  • familyName
  • middleName
  • displayName
  • nickName
  • title
  • preferredLanguage
  • locale
  • timezone
  • primary email
  • phoneNumbers

Supported Group Fields

  • displayName
  • members


  • The Brivo Okta integration does not support administrator provisioning.
  • It is required that users are in a general access group to facilitate creating a user, and other groups for access. This step is necessary.
  • Password syncing is not supported. Brivo Access administrator passwords are maintained in Access; they are not copied from Okta.
  • A group cannot have another group as a member.
  • Group names are not unique and can be duplicated in the Brivo Access account.
  • SSO is not included with this subscription and must be purchased as a separate subscription.
  • Brivo is unable to provision groups with more than 10,000 users.

Integrating into an existing Brivo Access account

If Okta will manage existing Brivo Access users, you must enter the Okta User IDs into Brivo Access prior to the integration to prevent the creation of duplicate Brivo Access users. Please contact Brivo Professional Services ( prior to proceeding.

How did we do?

BMP Provisioning with Identity Connector for Okta