multi-router.aidocs

User Provisioning (SCIM)

LifecycleEnterprise

What Multi-Router does when the directory adds, updates, deactivates, deletes and reactivates people.

The lifecycle is the path a person takes as the identity provider changes them, from arrival to suspension and back. Multi-Router applies each directory change to the matching person, and records it on the Activity tab of the People page with the directory as the actor.

Directory changes

Each directory change has this effect in Multi-Router:

Directory changeEffect
A person is addedMatched to an existing person by email, or added as Not set up. Rules then apply under the arrival setting.
A person already invited by hand is addedThey stay Invited, and their invitation keeps its grants as admin grants.
Name or attributes changeThe person's attributes update, and their name too while their directory email matches their Multi-Router email. Rules are checked again under the arrival setting.
Email changesA Review item; the person keeps their Multi-Router email.
Group membership changesRules are checked again for the person.
A person is deactivatedAn active person is suspended: their sessions end, and the routers and API keys of the tools they set up from the Portal are disabled.
A person is deletedThe same as deactivation. The person is suspended, and stays in Multi-Router.
A person is reactivatedA person the directory suspended returns to active, and their tools' routers and API keys are enabled again.

Suspension

Suspension stops a person's access while keeping their history. A suspended person's dashboard and Portal sessions end on their next request, and the routers and API keys of the tools they set up from the Portal are disabled, so tools such as Claude Code stop working at once. Invited and Not set up people who are deactivated are marked inactive, which blocks their sign-in and their invitation.

The directory can suspend anyone except the account owner. Removing a person from Multi-Router entirely is an admin action on the People page, called offboarding.

Reactivation

Reactivating a person in the identity provider restores a person whom the directory suspended, with their routers and API keys, and checks the rules for them again. A person an admin suspended by hand stays suspended until an admin restores them. A person who was offboarded and is pushed again arrives as a new Not set up person.

Review and NotificationsSCIM Endpoint
Was this helpful?