> ## Documentation Index > Fetch the complete documentation index at: https://docs.livingsecurity.com/llms.txt > Use this file to discover all available pages before exploring further. # SCIM and Google Workspace > What Google Workspace can and cannot provision to Living Security SCIM, and the other ways to keep Google Workspace people in Living Security. > [!NOTE] > > **Which SCIM setup applies to you?** These pages describe **Living Security SCIM**. Open the SCIM card in your settings. If the card shows **Set up SCIM**, or its **Mode** row says **Native SCIM**, these pages apply. If **Mode** says **Current SCIM**, your organization still uses the earlier SCIM setup. An admin can move it: see [Move from the earlier SCIM setup](https://docs.livingsecurity.com/features/settings/scim/connection.md#move-from-the-earlier-scim-setup). If the card says SCIM is set up and managed in the setup wizard, use [SCIM Provisioning](https://docs.livingsecurity.com/features/settings/scim.md). Google Workspace provisions users only to apps it supports. In most Google Workspace accounts it cannot send SCIM to a base URL and token you enter, so it cannot connect to Living Security SCIM on its own. ## What Google Workspace offers * **Catalog apps.** Google Workspace provisions users to apps in its own catalog with connectors Google builds. Living Security SCIM is not one of these connectors. * **Custom SCIM profiles.** Google offers automated provisioning to a custom SAML app that supports SCIM 2.0 as a beta, for a limited number of customers. If your account has it, the app's details page in the Admin console shows **Autoprovisioning**. Living Security has not tested Google Workspace custom SCIM profiles. Living Security SCIM follows the SCIM 2.0 standard (RFC 7643 and RFC 7644), so a standard SCIM 2.0 client should work. ## If your Admin console shows Autoprovisioning **1. Create the SCIM token in Living Security** On the SCIM card, select **Set up SCIM**. Copy the **SCIM base URL** and the **Bearer token**. You can't see the token again. See [Set up a SCIM connection](https://docs.livingsecurity.com/features/settings/scim/connection.md). **2. Set up autoprovisioning** Open the Living Security SAML app in the Google Admin console, then **Autoprovisioning**. Enter the SCIM base URL and the token as a bearer token, as Google's custom SCIM profile setup asks. **3. Map the attributes** Map the primary email to `userName` and to `emails[type eq "work"].value`, and map first name, last name, job title and department. See the [SCIM attribute reference](https://docs.livingsecurity.com/features/settings/scim/attributes.md). **4. Test with one person** Turn on the app for one organizational unit or group that holds only your test person, and follow [Test your SCIM setup](https://docs.livingsecurity.com/features/settings/scim/testing.md). ## If it does not Use one of these instead: * **Another identity provider that reads Google Workspace.** For example, JumpCloud and Okta can import people from Google Workspace and send them to Living Security with SCIM. See [Set up JumpCloud](https://docs.livingsecurity.com/features/settings/scim-jumpcloud.md) and [Set up Okta](https://docs.livingsecurity.com/features/settings/scim-okta.md). * **SSO with just-in-time sign-in.** Set up SSO with Google Workspace as the identity provider. Living Security creates each person at their first sign-in. Just-in-time sign-in does not update profiles or deactivate anyone, so remove leavers in **Workforce → People** yourself. See [SCIM, SSO and just-in-time sign-in](https://docs.livingsecurity.com/features/settings/scim/overview.md#scim-sso-and-just-in-time-sign-in). * **Other directory sources.** See [SCIM Provisioning](https://docs.livingsecurity.com/features/settings/scim.md) for the other ways to bring people into Living Security. ## Test your setup If you use autoprovisioning, follow [Test your SCIM setup](https://docs.livingsecurity.com/features/settings/scim/testing.md): check the **Checklist** tab, provision one person, read the **Attributes** tab, and have the person sign in. ## Troubleshoot * **No Autoprovisioning section.** Your account does not have Google's custom SCIM profiles. Use one of the options in [If it does not](#if-it-does-not). * **`401` ([LS-SCIM-1001](https://docs.livingsecurity.com/features/settings/scim/errors.md#ls-scim-1001)).** Copy the SCIM base URL and a current token from the SCIM card again. * **No usable email ([LS-SCIM-1107](https://docs.livingsecurity.com/features/settings/scim/errors.md#ls-scim-1107)).** Map the primary email to `emails[type eq "work"].value`. Every code is in the [SCIM error reference](https://docs.livingsecurity.com/features/settings/scim/errors.md). ## Related * [SCIM attribute reference](https://docs.livingsecurity.com/features/settings/scim/attributes.md) * [Test your SCIM setup](https://docs.livingsecurity.com/features/settings/scim/testing.md) * [SCIM error reference](https://docs.livingsecurity.com/features/settings/scim/errors.md) * [API reference and limits](https://docs.livingsecurity.com/features/settings/scim/api-reference.md) ## Related topics - [Google Workspace integration setup](https://docs.livingsecurity.com/integrations/google-workspace.md) - [Living Security SCIM](https://docs.livingsecurity.com/features/settings/scim/overview.md) - [Set up a SCIM connection](https://docs.livingsecurity.com/features/settings/scim/connection.md) This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.