> ## Documentation Index
> Fetch the complete documentation index at: https://docs.supamodel.io/llms.txt
> Use this file to discover all available pages before exploring further.

# Sign in with Google

> Let your team sign in to Supamodel with their Google Workspace accounts, and choose who controls access.

## What this is

Your team can sign in to Supamodel with their Google work account instead of a separate username and password. This works everywhere you sign in to Supamodel, including the Supamodel connector in Claude.

Google always checks who someone is. The choice you make is **who decides which people are allowed in**:

* **Option 1: Supamodel manages the access list.** You tell us who should have access, and we add or remove them for you.
* **Option 2: You manage access in Google.** You choose who has access from your Google Admin console, for example with a Google group. Anyone you allow is set up in Supamodel automatically the first time they sign in.

Both options only allow accounts from your company's Google Workspace. Personal Gmail accounts can never sign in.

## Compare the options

| | Option 1: Supamodel manages access | Option 2: You manage access in Google |
| - | - | - |
| **Who decides who gets in** | Supamodel, from a list you send us | You, in your Google Admin console |
| **Giving someone access** | Email us their name and work email | Add them to a Google group or organisational unit |
| **Removing access** | Email us | Remove them from the group, or suspend their Google account |
| **How fast changes apply** | Usually the same working day | Usually minutes, but Google can take up to 24 hours |
| **Where you set it up** | Google Cloud console | Google Admin console |
| **Who on your side sets it up** | Someone who can create a project in Google Cloud | A Google Workspace super admin |
| **Setup time** | About 15 minutes | About 20 minutes |
| **What you send us** | A client ID, a client secret and a list of people | A metadata file |

## Which option should you choose?

**Choose option 1 if:**

* Only a few people need access, and that list rarely changes.
* You don't have a Google Workspace super admin available, or you would rather not change settings in Google Admin.
* You want Supamodel to keep track of who has access.

**Choose option 2 if:**

* You already manage access to other tools with Google groups or organisational units.
* People join and leave the team often, and you want to make changes yourself without waiting for us.
* You want offboarding to happen in one place: when you remove someone in Google, their Supamodel access goes too.

> [!NOTE]
>
> In both options, suspending or deleting someone's Google account stops them signing in to Supamodel. In option 1, ask us to remove them as well so the list stays tidy.

## What your team sees

The sign-in experience is the same for both options:

1. Your colleague clicks **Connect** (or signs in) and the Supamodel sign-in page opens.
2. They type their work email.
3. Supamodel sends them to Google. If they are already signed in to Google, they may not need to do anything else.
4. Google sends them back, and they are signed in.

If someone isn't allowed in, the sign-in stops and they see a message saying they don't have access. No account is created for them.

## Switching over safely

Your current login keeps working while we set this up. We test with one person from your team first. Nobody else is affected until that test passes. We agree a date with you before switching off the old login.

## Set it up

> [card] [Option 1: Supamodel manages access](https://docs.supamodel.io/google-sso/supamodel-managed.md)
>
> Create a Google sign-in client and send us your access list.

> [card] [Option 2: You manage access in Google](https://docs.supamodel.io/google-sso/google-managed.md)
>
> Add Supamodel as an app in Google Admin and choose who can use it.

## Need help?

Contact us at [hello@supamodel.io](mailto:hello@supamodel.io).


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.