Skip to main content

SCIM provisioning

SCIM 2.0 lets your directory - Microsoft Entra ID, Okta and others - create workspace members, keep their roles in step with directory groups, and suspend them when they leave.

Create a provisioning token​

A workspace owner creates a token through the workspace API:

POST /api/v1/sso/scim-tokens
Content-Type: application/json

{
"label": "Entra provisioning",
"default_role": "viewer",
"group_role_map": { "Murmle Creators": "creator", "Facilitators": "presenter" }
}

The response contains the token, shown once, and the SCIM base URL to paste into your directory, ending in /scim/v2. GET /api/v1/sso/scim-tokens lists tokens without their secrets, and DELETE /api/v1/sso/scim-tokens/<id> revokes one. Each of these is recorded in the audit log.

Roles from groups​

  • group_role_map maps directory group names to roles; matching ignores capitals. The first group in a person's list that is in the map decides their role.
  • Anyone in no mapped group gets the token's default_role (viewer by default).
  • Roles are limited to creator, presenter, analyst and viewer. A map or default naming owner or admin falls back to viewer: a group someone can add themselves to must never mint a member who can delete the workspace.
  • An existing owner or admin is never demoted by a sync.
  • A role change replaces the previous role, so someone moving from one team to another ends up with the second team's role, not both.

Groups are read from each user's groups attribute, which is what Entra ID and Okta send.

De-provisioning is a suspension​

Deleting a user, or setting active to false, suspends their membership of this workspace. It never deletes them:

  • their activities, sessions and audit history stay intact, which is exactly when an audit trail matters;
  • they may be an active member of another workspace, and this workspace's directory must not disable them everywhere.

A suspended member loses all access to the workspace immediately. An owner cannot be suspended through SCIM.

What is supported​

EndpointOperations
/ServiceProviderConfigGET
/UsersGET (with userName eq "..." or emails.value eq "..." filters, up to 200 per page), POST
/Users/<id>GET, PUT, PATCH (the active attribute), DELETE

There is no /Groups endpoint: group membership reaches Murmle through each user's groups attribute. A directory that also tries to sync groups as resources will report that part as unsupported. Users provisioned by SCIM have no personal workspace; they can sign in through the workspace's single sign-on.