# Provision people from your identity provider

> Add and remove members automatically with SCIM from Okta, Google Workspace or Entra ID.

Source: https://diakrin.com/docs/provisioning

Your identity provider (IdP) can add and remove Diakrin members automatically using SCIM 2.0. Joiners get membership without an invitation; when someone leaves, their access ends on the IdP's next sync.

Owners and administrators set this up under **Settings → Provisioning**.

> [!SELF-HOSTED]
> SCIM provisioning is not yet qualified on self-hosted installations. The owner creates accounts under **Finish setup → Secure your workspace**, or assigns company OIDC subjects to accounts.

```diagram provisioning
Your identity provider stays the source of truth for who works at the company. Diakrin keeps control of roles and app access.
```

## What provisioning does

- **New person in the IdP app:** Diakrin reserves a **Member** seat for their email. When they first sign in with that verified email, they join your organization. If they are already a member, Diakrin links them.
- **Person deactivated or removed:** their membership is removed through the same path as removing a member in Diakrin. Project access is revoked and their coding-tool (MCP) tokens stop working immediately.
- **Groups pushed from the IdP:** they appear read-only as **Directory groups** under **Settings → Members**. A business access group can follow a directory group so its members stay in sync.

Provisioning never grants or removes **Owner**, **Admin** or **Technical administrator**. Change those roles in Diakrin. If your IdP tries to deactivate one of these people, Diakrin refuses and records the refusal under **Recent activity**; demote them in Diakrin first.

## Connect

1. Open **Settings → Provisioning** and select **Generate token**. Copy the token now; it is shown once.
2. Copy the **SCIM base URL**. It ends with your organization ID.
3. Configure your identity provider (below) with the base URL and the token as an OAuth bearer token.
4. Assign people and push groups. The status changes from **Waiting for first sync** to **Connected** after the first call.

Only one token is active. **Rotate token** issues a new one and stops the old one immediately; update your IdP right away. **Revoke token** stops provisioning; existing members keep their access.

## Okta

1. In the Okta Admin Console, open your Diakrin app (or create an app integration with SCIM provisioning).
2. Under **Provisioning → Integration**, set **SCIM connector base URL** to the SCIM base URL, **Unique identifier field for users** to `userName`, and enable **Push New Users**, **Push Profile Updates** and **Push Groups**.
3. Set **Authentication Mode** to **HTTP Header** and paste the token.
4. Under **Provisioning → To App**, enable **Create Users**, **Update User Attributes** and **Deactivate Users**.
5. Assign people, then use **Push Groups** for the groups you want in Diakrin.

## Google Workspace

Google Workspace offers auto-provisioning only for some apps. Open **Apps → Web and mobile apps**, select your Diakrin app and look for **Auto-provisioning**.

- If it is available, paste the SCIM base URL as the endpoint and the token as the access token, map **Primary email** to `userName` (Diakrin treats email case-insensitively), choose the groups in scope and turn it **On**. Suspended or removed users are deprovisioned.
- If it is not available for your app, keep using invitations for Google-managed people, or provision through another IdP that federates Google Workspace.

## Microsoft Entra ID

Open the enterprise application → **Provisioning → Automatic**. Use the SCIM base URL as **Tenant URL** and the token as **Secret Token**, then **Test Connection** and start provisioning.

## Limits

- Supported: Users and Groups, `PATCH`, and equality filters on `userName`, `externalId` and `displayName`. Bulk operations and sorting are not supported.
- Up to 200 results per page and 5,000 members per group. Requests are limited to 64 KiB.
- A business access group that follows a directory group can hold up to 500 people.
- Removing a person from your IdP removes them within one SCIM call. Directory-group changes reach bound access groups within five minutes.
