User Provisioning (SCIM)
OverviewEnterprise
Keeping Multi-Router's people and their access in step with your identity provider's directory.
User provisioning lets the company's identity provider, such as Okta, manage the people in Multi-Router. The identity provider sends people and groups to Multi-Router over SCIM 2.0, the standard protocol for directory sync: new hires appear in Multi-Router, changes to their name or department follow, and people deactivated in the identity provider are suspended in Multi-Router. Rules turn directory groups and attributes into access, such as an organization role or Portal access with a tools policy, so access follows the directory without manual invitations.
How it works
Provisioning connects three things:
| Part | Role |
|---|---|
| The directory | The identity provider pushes people and groups to Multi-Router's SCIM endpoint with a directory token. |
| Rules | Each rule matches people by a pushed group or an attribute such as department, and grants a bundle of access. |
| Review | Changes that need a person to decide, such as access that no longer matches any rule, wait in Review. |
A person's path through provisioning:
- The identity provider pushes the person. Multi-Router matches them to an existing person by email, or adds them as Not set up.
- Rules that match the person grant access, immediately or after approval, depending on the arrival setting.
- The person signs in through SSO and uses what they were granted, such as setting up Claude Code from the Portal.
- When the identity provider deactivates the person, Multi-Router suspends them and disables their routers and API keys.
Provisioning and SSO
User provisioning builds on single sign-on: it needs an SSO connection that is on, with a verified domain. While provisioning is connected, the directory decides who has access, and SSO signs people in with the access the directory and its rules granted. SSO's new-user access is set to invite-only for the duration, and returns to its earlier setting when provisioning is turned off. See Single Sign-On.
Built-in safeguards
Directory changes grant access and suspend people, and removing access is an admin decision:
| Safeguard | Behavior |
|---|---|
| Account admin grants | When a rule grants account admin, the person's rule access waits for an account admin's approval. |
| Lost matches | Access that no longer matches a rule goes to Review, where an admin keeps or removes it. |
| Account owner | The directory can suspend anyone in the account except the account owner. |
| Email changes | A changed email in the directory is shown in Review, and the person keeps their Multi-Router email. |
| Admin grants | Rules leave access granted by an admin as it is, and admins leave a rule's access to the rule. |
Related topics
The other pages in User Provisioning cover each part in detail:
| Page | Covers |
|---|---|
| Connecting Your Directory | Turning on provisioning, arrival settings, the endpoint and directory tokens. |
| Okta | Setting up provisioning in Okta. |
| Microsoft Entra ID | Setting up provisioning in Entra ID. |
| Ping Identity | Setting up provisioning in PingOne. |
| JumpCloud | Setting up provisioning in JumpCloud. |
| Other Directories | Connecting any SCIM 2.0 directory. |
| Rules | Granting access from groups and attributes. |
| Review and Notifications | Approvals, lost matches, email changes, and alerts. |
| Lifecycle | Arrival, updates, suspension, deletion and reactivation. |
| SCIM Endpoint | Resources, attributes, filters, PATCH and errors. |
| Troubleshooting | Connection health and common problems. |