# Google Workspace SCIM directory sync

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

Turn on Autoprovisioning for the app's custom SAML app in the Google Admin console, and Google pushes your people to this directory over SCIM.

:::caution[Beta: people only, and only in some Workspaces]
Only Workspaces that Google admitted to its custom SCIM profiles beta see Autoprovisioning on a custom SAML app. Google sends people only, never groups, does not send people on secondary domains and connects with a bearer token only. Connect Google, in the Google Workspace directory sync guide, is the recommended way: it reads people and groups from Google and works in every Workspace.
:::

:::note[Verification]
Verified on a real Google Workspace tenant on 2026-11-11.
:::

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="prerequisites"></a>

### Check that you can use Autoprovisioning

Set up single sign-on with Google first, as a custom SAML app. Sign in as a super admin. If the app's page has no Autoprovisioning (BETA) section, your Workspace is not in Google's beta; use Connect Google instead.

</li>

<li class="idp-step">

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

### Open the app's Autoprovisioning settings

In the Google Admin console, go to Menu > Apps > Web and mobile apps, add or open your custom SAML app, then select Autoprovisioning (BETA) > Configure autoprovisioning.

</li>

<li class="idp-step">

<a id="connect"></a>

### Paste the SCIM token and endpoint

Paste `{scim_token}` as the Access token and `{scim_base_url}` as the Endpoint URL. The token is shown once in this setup; generate a new one here if you lose it.

<div class="setup-values">

Paste into Google Workspace:

- SCIM base URL: `{scim_base_url}`
- SCIM bearer token: `{scim_token}`

</div>

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

</li>

<li class="idp-step">

<a id="scope"></a>

### Review the mapping and choose who is synced

Google pre-fills the attribute mapping from our schema; keep it. Optionally limit provisioning to members of chosen groups, then choose what happens when a user is suspended or deleted. Only people on your primary domain are sent.

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

</li>

<li class="idp-step">

<a id="test"></a>

### Test the connection

Select Test connection. Google creates, updates and deletes a test user in this directory; the test passes when all three succeed.

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

</li>

<li class="idp-step">

<a id="start"></a>

### Turn on Autoprovisioning

Switch Autoprovisioning on, and make sure the app is ON for the users you want synced. Google pushes people only; groups never arrive by this route.

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

</li>

</ol>

## Sources

- [About automated user provisioning (Google Workspace Admin Help)](https://knowledge.workspace.google.com/admin/users/advanced/about-automated-user-provisioning), read on 2026-10-11
