multi-router.aidocs

User Provisioning (SCIM)

Connecting Your DirectoryEnterprise

Turning on user provisioning, choosing what happens when someone new arrives, and managing directory tokens.

Connecting a directory turns on user provisioning for the account and gives the identity provider an endpoint and a token to push people to. It is done on the User provisioning (SCIM) page, opened from Settings in the account, after single sign-on is set up and its domain verified.

Steps

Connecting takes a few minutes in Multi-Router and the identity provider:

  1. Set up SSO and verify its domain. See Setting Up SSO.
  2. Open Settings, then User provisioning (SCIM), and turn on User provisioning.
  3. Choose what happens When someone new arrives.
  4. Select Save. Multi-Router turns on provisioning and issues a directory token.
  5. Copy the SCIM base URL into the identity provider, then copy the token with Copy on its row and paste it there too.
  6. Run the identity provider's connection test. The connection health panel then shows the identity provider's contact.

When someone new arrives

The arrival setting decides what rules do each time the directory pushes a person, on arrival and on every later update:

SettingBehavior
Apply rules automaticallyMatching rules grant access at once. Access that includes account admin waits for approval.
Require admin approvalMatching rules create approval requests, and access starts when an admin approves.
Do nothingRules grant nothing, and people get access when an admin grants it. Access that no longer matches a rule still goes to Review. This is the default.

To change the arrival setting while provisioning is on, turn provisioning off and on again. See Rules.

The SCIM base URL

The SCIM base URL is the address the identity provider sends requests to. It belongs to the account and has the form https://api.multi-router.ai/scim/v2/acc_7Tq2Wd9KxP. The page shows it with a Copy button.

Directory tokens

A directory token is the credential the identity provider sends with each request, in the Authorization header. Tokens start with mr_scim_ and work only for the SCIM endpoint of their own account. The page lists each token with its first characters, when it was created and when it was last used:

ActionEffect
Issue tokenCreates a token. Up to two can be enabled at once.
CopyCopies the full token to the clipboard.
DisableStops the token from working. Enable restores it.
DeleteRemoves a disabled token permanently, after a confirmation.

A directory token can suspend everyone in the account except the owner, so it is kept in the identity provider and nowhere else. To rotate a token: issue a new one, copy it into the identity provider, confirm a successful sync, then disable the old one.

Connection health

example-co · acc_7Tq2Wd9KxP

Account Settings

User provisioning (SCIM)

On. Okta can add, update and suspend people in this account.

When someone new arrives

To change this, turn user provisioning off and on again.

Connection health

Okta last contacted us 10/1/2026, 9:42:18 AM

Last request succeeded · 128 recorded · Multi Router keeps the last 500 recorded requests

Refresh status

Endpoint and tokens

Copy this account-scoped URL into your directory provider. A token from another account is refused.

Copy

A directory token can suspend everyone except the account owner. Rule changes do not automatically remove existing access; removals require review.

Up to two tokens can be enabled at once for rotation. Copy the new token into Okta, confirm a sync there, then disable the old one.

Issue token
  • mr_scim_Xq7v••••••••••••••••••••••••••••Copy
    Created 9/14/2026 · Last used 10/1/2026, 9:42:18 AM
    DisableDelete

Notification rules

Send one batched notification when matching directory events occur.

Add notification rule
EventRecipientsStatusActions
Approval neededAll account adminsOn
Turn offEditDelete
Connection failureit-ops@example.com, security@example.comOn
Turn offEditDelete

2 of 20 rules used.

Failed background work

Refresh status

No failed background work.

Recent requests

Refresh history

Use your directory provider’s connector test. No request bodies, person fields, resource IDs, or token details appear here.

  • PATCH Users · 200Request req_Vb7Kq2Xn9TzR4wLp · 10/1/2026, 9:42:18 AM
  • GET Users · 200Request req_H3mPq8Zs1YcN6dFu · 10/1/2026, 9:42:17 AM
  • POST Users · 201Request req_Lw5Rt0Gk7JxB2vQe · 10/1/2026, 9:31:04 AM
  • PATCH Groups · 200Request req_Ce9Nz4Ua6MhW1sKy · 10/1/2026, 9:31:02 AM
User provisioning on for Okta: connection health, the SCIM base URL, a directory token, notification rules and recent requests. Select to enlarge.

The connection health panel shows whether the identity provider is reaching Multi-Router:

StateMeaning
Waiting to hear from your directoryProvisioning is on, and no request has arrived yet.
{provider} last contacted us {time}Requests are arriving. The detail line shows whether the last one succeeded.
Directory connection stopped workingA request used a disabled token, or three requests in a row failed on the server side or reached the wrong account. The reason is shown.

Recent requests lists the latest requests with their method, resource, status, reason and request id, and Refresh status updates the panel. A request Multi-Router refuses as invalid shows in Recent requests and leaves the connection healthy. The panel returns to healthy on the next successful request. See Troubleshooting.

Turning provisioning off

Turning off User provisioning disables every directory token and returns SSO's new-user access to its earlier setting. People and their access stay as they are. Turning provisioning on again re-enables the newest token.

While provisioning is on, the SSO connection's domain, new-user access and the connection itself stay fixed; turn provisioning off to change them. Requests that reach the endpoint while provisioning is off return 401 with invalid bearer token, because every token is disabled.

OverviewOkta
Was this helpful?