Skip to main content
Hosted SCIM connects Opal to 1Password’s hosted provisioning with a bearer token. Nothing to deploy. Opal syncs people and SCIM-managed groups, and can create and suspend people when you choose read and write access. Vaults and vault permissions stay on the self-hosted connector. Hosted SCIM can’t see them, because vault data is end-to-end encrypted. Not sure which path to use? Start on the 1Password overview and answer two questions.

Supported resources

Hosted SCIM does not sync vaults, vault permissions, Owners, or Administrators. Opal only sees the groups that hosted provisioning manages. 1Password doesn’t support nested groups.

How people and groups map to Opal

  • People: each active 1Password person appears as a user on the app. Creating a person in Opal invites them in 1Password when their email domain is under Invitations > Allowed domains. Removing access suspends the person instead of deleting them, so their account and vaults can be restored.
  • Groups: each SCIM-managed group appears as a group. Granting group access adds the person as a member. Owners and Administrators aren’t available over Hosted SCIM.
  • Read only vs read and write: read only syncs people and groups without changing 1Password. Read and write also lets Opal create and suspend people and change group membership.

Requirements

Before you begin, you’ll need:
  • A 1Password Business account with hosted provisioning available
  • Access in 1Password to Integrations > Hosted provisioning
  • Email domains for people you will invite listed under Invitations > Allowed domains
  • To be an Opal Admin
If an identity provider already provisions this 1Password account, don’t regenerate its SCIM token. Regenerating the token stops the identity provider from syncing. Use the existing token only if your identity provider team agrees Opal should share it, or set up Hosted SCIM on an account that isn’t already provisioned that way.

Configuration steps

1. Open Hosted provisioning in 1Password

  1. In 1Password, go to Integrations > Hosted provisioning.
  2. Choose Other (Beta), then Not listed.
  3. Copy the bearer token.
  4. Note the SCIM URL host for your account’s region, for example provisioning.1password.com, provisioning.1password.ca, provisioning.1password.eu, or provisioning.ent.1password.com.

2. Create the 1Password app in Opal

  1. In Opal, go to Inventory > Add App, and select Connect on the 1Password tile under SaaS Apps.
  2. On How do you want to connect 1Password?, choose Hosted SCIM, then Continue.
  3. Fill in:
  1. Select Create. Opal checks that it can read people with the token.

3. Import people and groups

On the app’s Assets tab, import the people and groups you want to manage. Only SCIM-managed groups appear. Owners and Administrators do not. Users can now request group membership. With Read and write, Opal can also create and suspend people according to your access policies.

Using Hosted SCIM with the self-hosted connector

Add the self-hosted connector as a second app when you need vault-level grants. Keep people lifecycle on Hosted SCIM, and vault access on the connector. Don’t let both apps write membership for the same group. That can overwrite changes in 1Password.

Troubleshooting

Confirm the bearer token is from Integrations > Hosted provisioning, not a different 1Password API credential. Confirm SCIM URL host matches your account region. If you recently regenerated the token, wait a moment and try again with the new value.
Hosted SCIM only lists groups that provisioning manages. Built-in Owners and Administrators, and groups that can recover accounts or manage all groups, aren’t available. Use the self-hosted connector for those groups if you need them in Opal.
1Password only accepts people whose email domain is under Invitations > Allowed domains. Add the domain there, then try again. If the person already exists but is suspended, Opal reactivates them instead of creating a duplicate.
Last modified on November 20, 2026