Skip to content
Dashboard
Theme
Theme

Google Workspace SCIM directory sync

Set up Google Workspace (SCIM, beta) directory sync

View Markdown

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.

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.

  1. 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.

  2. Open the app’s Autoprovisioning settings

    Section titled “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.

  3. 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.

    Paste into Google Workspace:

    • SCIM base URL: {scim_base_url}
    • SCIM bearer token: {scim_token}

    Fixes: scim_token_invalid

  4. Review the mapping and choose who is synced

    Section titled “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

  5. 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

  6. 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