> For the complete documentation index, see [llms.txt](https://docs.currents.dev/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.currents.dev/dashboard/administration/sso-saml2.0/scim-user-provisioning.md).

# SCIM User Provisioning

Provision and de-provision users in Currents using SCIM v2

Currents supports [SCIM v2 ](https://datatracker.ietf.org/doc/html/rfc7644)to automatically provision and de-provision users.

SCIM is requested alongside SSO: select **Also set up SCIM provisioning** in step 3 of [Setting Up SSO](/dashboard/administration/sso-saml2.0/setting-up-sso.md), and the same request covers both. Organizations that already have SSO enabled can ask Currents support to add SCIM instead.

Once enabled by Currents team, organization admins will be able to find the **SCIMv2 Endpoint** and **Authorization Bearer Token** on the **Manage Team** section at <https://app.currents.dev>.

<figure><img src="https://3745692499-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FqmFDEiUa9mr11LUlxDnt%2Fuploads%2FXpp13FIX5ZFGIT5EvOGt%2Fscim-provisioning.png?alt=media&amp;token=59d3d86f-507c-48aa-b8c9-45f94270aef8" alt=""><figcaption><p>SCIM details can be fetched in the Currents app by Org Admins</p></figcaption></figure>

### Supported features

Currents supports User resource provisioning using SCIM. **Group resources are not supported**. Only users with an email address that matches the domains configures in the [SSO setup](/dashboard/administration/sso-saml2.0.md) are supported.

When a user is deactivated, Currents removes the user from the team member list. When a user is activated, they are not added to the team member list in Currents until after they login.

The following provisioning endpoints are supported:

* GET Users
  * List all users belonging to your organization in our system
  * Search for a specific user using SCIM filtering
* GET User
  * Get a specific user based on id
* POST User
  * Create a new user
* PUT User
  * Update an existing user's active status or display name.
* DELETE User
  * Deactivates the user

### Managed Provisioning

We are maintaining a Managed SCIM provisioning settings for popular providers:

* [Okta Provisioning](/dashboard/administration/sso-saml2.0/okta/okta-user-provisioning.md)
* [JumpCloud Provisioning](/dashboard/administration/sso-saml2.0/jumpcloud/jumpcloud-user-provisioning.md)

### Manual SCIM Configuration

Use the settings below to manually configure your SCIMv2 client.

| Name                         | Value                                                                            |
| ---------------------------- | -------------------------------------------------------------------------------- |
| SCIMv2 Base Url              | Different for each org. It is available in the **Manage Team** dashboard section |
| Auth Method                  | Authorization Header                                                             |
| Auth Type                    | Bearer Token                                                                     |
| `userName` mapping           | email                                                                            |
| Mandatory mapped fields      | `name.givenName`, `name.familyName`, `emails`, `active`                          |
| Optional non-writable fields | `name.formatted`, `displayName`                                                  |

In case of an error, please collect the error detials and contactour support for assistance.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.currents.dev/dashboard/administration/sso-saml2.0/scim-user-provisioning.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.