# JumpCloud SCIM directory sync

<!-- Generated by scripts/generate.ts. Do not edit. -->

Turn on identity management with SCIM for your JumpCloud application, connect it with the URL and token from this setup and bind the groups to sync.

:::caution[Verification]
Not yet verified on a real JumpCloud tenant. It was written from the public JumpCloud documentation, so labels in the admin console may differ slightly.
:::

The values in braces, such as `{scim_base_url}`, are specific to your connection. The setup link from the application you are connecting shows them with a copy button. The same steps appear there.

## Steps

<ol class="idp-steps">

<li class="idp-step">

<a id="app"></a>

### Open your JumpCloud application

In the JumpCloud Admin Portal, open SSO Applications and select the app you use for single sign-on with this setup. Open its identity management tab and choose SCIM.

:::caution[Labels not confirmed in step 1]
The JumpCloud support pages refused automated reads on 2026-10-11 (HTTP 403); every label in this guide is written generically.
:::

</li>

<li class="idp-step">

<a id="base-url"></a>

### Enter the SCIM base URL

Paste `{scim_base_url}` into the base URL field.

<div class="setup-values">

Paste into JumpCloud:

- SCIM base URL: `{scim_base_url}`

</div>

:::caution[Labels not confirmed in step 2]
Field label not confirmed from a JumpCloud source on 2026-10-11.
:::

</li>

<li class="idp-step">

<a id="token"></a>

### Enter the bearer token

Choose bearer token authentication and paste `{scim_token}`. The token is shown once in this setup; generate a new one here if you lose it.

<div class="setup-values">

Paste into JumpCloud:

- SCIM bearer token: `{scim_token}`

</div>

Fixes: [`scim_token_invalid`](/errors/scim_token_invalid/)

:::caution[Labels not confirmed in step 3]
Field label not confirmed from a JumpCloud source on 2026-10-11.
:::

</li>

<li class="idp-step">

<a id="activate"></a>

### Test and activate

Test the connection, then activate and save.

Fixes: [`first_scim_request_pending`](/errors/first_scim_request_pending/)

:::caution[Labels not confirmed in step 4]
Button labels not confirmed from a JumpCloud source on 2026-10-11.
:::

</li>

<li class="idp-step">

<a id="groups"></a>

### Bind the groups to sync

JumpCloud provisions the members of the user groups bound to the app. Bind the groups whose members should be synced.

Fixes: [`scim_user_out_of_domain`](/errors/scim_user_out_of_domain/)

:::caution[Labels not confirmed in step 5]
Group-scoped provisioning is documented by JumpCloud; the labels are not confirmed.
:::

</li>

</ol>

## Sources

- [Provision and manage users and groups in apps using custom SCIM (JumpCloud Support)](https://jumpcloud.com/support/provision-and-manage-users-and-groups-in-apps-using-custom-scim-identity-management-integration), read on 2026-10-11
