Skip to content

Directory sync (SCIM) ​

With directory sync, your identity provider manages the people of your linkable.id account through SCIM:

  • People assigned to linkable.id in your identity provider get an account, ready to sign in with single sign-on.
  • Their name and email stay up to date.
  • When someone is disabled, unassigned or deleted there, they're suspended here at once: signed out everywhere, their API tokens and Claude connections stopped, and their work kept. Re-enabling them brings them back.
  • Their workspaces and roles can follow their groups in your identity provider.

Availability: the Enterprise plan, with single sign-on; works with Microsoft Entra ID and Okta. linkable.id support sets it up with your IT team (see For your IT team).

Google Workspace can't send SCIM to apps outside Google's own catalog, so it isn't supported. With Require SSO, someone suspended in Google can't sign in; a super admin suspends them here to stop their tokens and connections too. To sync automatically, you can put Okta or Microsoft Entra ID in front of Google Workspace.

Who your identity provider manages ​

Only people on your company's single sign-on domains. When it sends someone who already has a linkable.id user (added by hand or by an earlier SSO sign-in), that user is taken over: their work and history stay. People outside your domains, like an agency, are never touched.

Your identity provider never makes anyone a super admin, and never suspends a break-glass account or changes its email, or a super admin's. In Users, the Managed by column shows who your identity provider manages, and someone it switched off shows Suspended by your identity provider: reactivate them there, not here.

Mapping groups to workspaces ​

Super admins map groups on Settings → Directory sync. Each mapping is a group, a workspace and a role: for example, "Sales" → the Sales workspace → Editor.

  • New people land in your account's default workspace and role.
  • Once a workspace has a mapping, the people your identity provider manages are in it exactly while they're in a mapped group, with the roles of all their mapped groups there. Leaving the group removes them from that workspace and stops their Claude connections and API tokens for it.
  • Workspaces without a mapping are never changed: add and remove people there as usual.
  • A workspace where someone is super admin is never changed for them.
  • You can map groups only to workspaces where you're a super admin, and never to the super admin role.

Map your groups before assigning people to linkable.id in your identity provider, so everyone lands in the right workspaces from the start. In a workspace that follows groups, people your identity provider manages show "Managed by your identity provider", and they're added or removed through their groups rather than by hand.

For your IT team ​

Ask linkable.id support for your SCIM base URL (https://your-admin-domain/scim/v2) and SCIM token, through a secure channel. Single sign-on must already work.

Microsoft Entra ID: Microsoft doesn't allow provisioning on the app registration you use for single sign-on, so provisioning gets a second app: Enterprise applications → New application → Create your own application → "Integrate any other application you don't find in the gallery (Non-gallery)", named for example "linkable.id provisioning". Assign the same groups to both apps, so everyone who is provisioned can also sign in.

  1. In the new app, Provisioning → mode Automatic. Tenant URL: the SCIM base URL. Secret token: the SCIM token. Test connection, then save.
  2. Mappings → Provision Microsoft Entra ID Users: keep userPrincipalName → userName (it must be the person's work email on your domains) as the matching attribute. linkable.id ignores attributes it doesn't keep, like addresses and phone numbers; you can remove them.
  3. Mappings → Provision Microsoft Entra ID Groups: on, if you use groups.
  4. Settings → Scope: "Sync only assigned users and groups". Assign the people and groups, then start provisioning.

Okta (the OIDC app integration you use for single sign-on, if it was created with the App Integration Wizard; Okta doesn't support SCIM on OIDC integrations created in its Classic experience, so in that case create a new one):

  1. General → Provisioning: SCIM. SCIM connector base URL: the SCIM base URL. Unique identifier field for users: userName. Supported provisioning actions: push new users, push profile updates, push groups. Authentication mode: HTTP Header, with the SCIM token as the bearer token. Test connector configuration, then save.
  2. Provisioning → To App: enable create users, update user attributes and deactivate users.
  3. Push Groups: push the groups you want to map.

Menu names in the admin consoles change over time; the values above are what matters.

If something goes wrong ​

Your identity provider's provisioning logs show linkable.id's answer for each person:

  • "The email is not on this account's single sign-on domains": the person's userName isn't on your company's domains.
  • "A user with this email already exists and can't be provisioned": the email belongs to a deleted user; a super admin restores or removes it in Users.
  • "The account's plan has no room for another user": your plan's user limit is reached.
  • "This account's email can't be changed through SCIM": a super admin's or break-glass account's email; a super admin changes it here.

With Claude ​

Claude can't manage directory sync yet: that stays in the panel.