multi-router.aidocs

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:

PartRole
The directoryThe identity provider pushes people and groups to Multi-Router's SCIM endpoint with a directory token.
RulesEach rule matches people by a pushed group or an attribute such as department, and grants a bundle of access.
ReviewChanges that need a person to decide, such as access that no longer matches any rule, wait in Review.

A person's path through provisioning:

  1. The identity provider pushes the person. Multi-Router matches them to an existing person by email, or adds them as Not set up.
  2. Rules that match the person grant access, immediately or after approval, depending on the arrival setting.
  3. The person signs in through SSO and uses what they were granted, such as setting up Claude Code from the Portal.
  4. 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:

SafeguardBehavior
Account admin grantsWhen a rule grants account admin, the person's rule access waits for an account admin's approval.
Lost matchesAccess that no longer matches a rule goes to Review, where an admin keeps or removes it.
Account ownerThe directory can suspend anyone in the account except the account owner.
Email changesA changed email in the directory is shown in Review, and the person keeps their Multi-Router email.
Admin grantsRules leave access granted by an admin as it is, and admins leave a rule's access to the rule.

The other pages in User Provisioning cover each part in detail:

PageCovers
Connecting Your DirectoryTurning on provisioning, arrival settings, the endpoint and directory tokens.
OktaSetting up provisioning in Okta.
Microsoft Entra IDSetting up provisioning in Entra ID.
Ping IdentitySetting up provisioning in PingOne.
JumpCloudSetting up provisioning in JumpCloud.
Other DirectoriesConnecting any SCIM 2.0 directory.
RulesGranting access from groups and attributes.
Review and NotificationsApprovals, lost matches, email changes, and alerts.
LifecycleArrival, updates, suspension, deletion and reactivation.
SCIM EndpointResources, attributes, filters, PATCH and errors.
TroubleshootingConnection health and common problems.
TroubleshootingConnecting Your Directory
Was this helpful?