> ## 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. # Option 1: Supamodel manages access > Set up Google sign-in for Supamodel, with Supamodel keeping the list of who is allowed in. ## How this works You create a small "Sign in with Google" client in your Google Cloud account and send us its details. You also send us the list of people who should have access. We add each person to Supamodel. When someone on the list signs in, Google checks who they are and Supamodel lets them in. Anyone not on the list is refused, even if they work at your company. Not sure this is the right option? See [Sign in with Google](https://docs.supamodel.io/google-sso/overview.md) to compare it with option 2. ## Before you start You need: * A Google Workspace account at your company. * Permission to create a project in the Google Cloud console. If you can't, ask your Google Workspace admin. * The **redirect URL** we sent you. It looks like `https://auth.supamodel.io/...`. If you don't have it, ask us. ## Set up the Google sign-in client **1. Open the Google Cloud console** Go to [console.cloud.google.com](https://console.cloud.google.com) and sign in with your work account. Select a project, or create a new one called `supamodel-sso`. When you create it, check that **Location** shows your company's organisation, not **No organisation**. **2. Set up the consent screen** Go to **APIs & Services** > **OAuth consent screen**. In newer versions of the console this is under **Google Auth Platform** > **Branding** and **Audience**. Enter these details: * **App name**: `Supamodel` * **User support email**: your email address * **Audience** (or **User type**): **Internal** * **Authorised domains**: add `supamodel.io` if the console asks for one You don't need to add any extra scopes. > [!WARNING] > > Make sure you choose **Internal**. This is what stops anyone outside your company signing in. If **Internal** isn't available, your project isn't inside your company's organisation. Go back to step 1. **3. Create the client** Go to **APIs & Services** > **Credentials** (or **Google Auth Platform** > **Clients**). Click **Create credentials** > **OAuth client ID**. * **Application type**: **Web application** * **Name**: `Supamodel` * **Authorised redirect URIs**: click **Add URI** and paste the redirect URL we sent you, exactly as it is Click **Create**. **4. Copy the client ID and secret** Google shows a **Client ID** and a **Client secret**. Copy both somewhere safe for the next step. If you close the window by accident, open the client from the credentials list to see them again. ## Send us the details **1. Send the client ID** Email the **Client ID** to [hello@supamodel.io](mailto:hello@supamodel.io). It isn't secret, so email is fine. **2. Send the client secret securely** We send you a secure, one-time link. Paste the **Client secret** into that link. > [!WARNING] > > Never send the client secret by email, chat or any other way. If you think it has been shared by mistake, delete the client in Google Cloud and create a new one. **3. Send your access list** Email us the people who should have access. For each person, include: * Their full name * The Google work email they sign in to Google with Use the address each person actually signs in with, not an alias or a group address. If the email doesn't match exactly, Supamodel refuses that person. ## Test and switch over **1. Test with one person** We book a short call with you. You sign in with Google while we check everything works. Your current login keeps working throughout. **2. Tell your team** Once the test passes, ask everyone on your list to reconnect. In Claude, they go to **Customize** > **Connectors** > **Supamodel**, click **Disconnect**, then **Connect**. Anyone who hasn't added the connector yet can follow [Connect Supamodel to Claude](https://docs.supamodel.io/claude-connector.md). On the sign-in page, they type their work email and continue with Google. **3. Agree a switch-off date** When everyone is using Google, we agree a date with you to switch off the old login. ## Give or remove access later To **give someone access**, email us their full name and Google work email. We let you know when they're added. To **remove someone's access**, email us their name and email. Once we remove them, they can't sign in again. They may stay connected for up to 12 hours, until their current session expires. > [!TIP] > > If someone leaves your company, suspending their Google account also stops them signing in to Supamodel straight away. Let us know too, so we can remove them from the list. ## Look after the Google client The Google client lives in your Google Cloud project. Make sure at least one other admin at your company knows it exists. If the person who created it leaves, the client keeps working, but someone needs to be able to manage it. Don't delete the client or the project. If you do, nobody can sign in to Supamodel with Google until you create a new one and send us the details. ## Troubleshooting > [accordion] Google says the app is restricted to users within its organisation > > The person is signing in with a personal Google account, or an account from a different company. Ask them to sign in with their work account. > [accordion] Supamodel says the person doesn't have access > > They aren't on the access list, or the email we have doesn't match the one they use with Google. Check which email they sign in to Google with, and send it to us. > [accordion] Google shows a redirect\_uri\_mismatch error > > The redirect URL in your Google client doesn't exactly match the one we sent. Open the client in Google Cloud and paste the URL again. Check there is no extra space or slash at the end. ## 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.