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

# Sign in to Beebole with Google — SSO and Domain Links

> Sign in to Beebole with a Google account, link your Google Workspace domains, auto-provision people, and require Google sign-in across your organization.

Google sign-in lets anyone in your organization sign in to Beebole with their existing Google account, which is convenient for teams already on Google Workspace. It is a built-in sign-in option — no administrator setup is required to use it. Linking your Google domains adds organization-level controls: automatic provisioning and the option to require Google sign-in for everyone.

<Info>
  This page covers the Google-specific controls. For the full picture of how sign-in and single sign-on work in Beebole — email codes, passkeys, and the **Single Sign-On** panel — see [Sign-in, passkeys, SSO, and API keys](/help/documentation/authentication).
</Info>

## Sign in with Google

Google sign-in is always available on the Beebole sign-in screen. Under **Or Sign in with**, click the **Google** button, then authenticate with your Google account. Beebole matches the Google account's email address to your Beebole profile, so both must use the same email address.

Because Google sign-in is built in, you do not need to turn anything on for your team to use it. Linking domains, described below, is optional and unlocks the organization-level controls.

## Link your Google domains

Linking a domain ties your Google Workspace organization to your Beebole account and enables the controls that follow. You configure this on the **Single Sign-On** panel of **Account Settings**, on the **Google** tab.

<Steps>
  <Step title="Open the Google tab">
    Go to **Settings** > **Account Settings**, open the **Single Sign-On** panel, and select the **Google** tab.
  </Step>

  <Step title="Add a domain">
    Type your organization's email domain in the **Linked domains** field and click **Add**. To unlink a domain, click **Remove** next to it. Changes save automatically.
  </Step>

  <Step title="Finish in Google Marketplace">
    Once a domain is linked, Beebole shows a **Go to Google Marketplace** link. Follow it to complete the setup in the Google Workspace Marketplace.
  </Step>
</Steps>

## Provision new people automatically

On the **Google** tab, turn on **Automatically create new users on first SSO login** to create a Beebole person automatically the first time someone with a matching linked domain signs in. With this setting off, a matching person must already exist in your Beebole account before they can sign in with Google. The setting saves automatically.

## Require Google sign-in

<Steps>
  <Step title="Open integration settings">
    Open **Settings** > **Single Sign-On** in your Beebole account, then switch to the **Google** tab.
  </Step>

  <Step title="Enable Google SSO">
    Locate the **Google** card and click **Connect**. Follow the OAuth prompts to authorize Beebole to verify your identity through Google.
  </Step>

  <Step title="Verify the connection">
    Once connected, the Google integration shows as active in your integration settings. Users in your account can now sign in using the **Sign in with Google** button on the login page.
  </Step>
</Steps>

To make Google the only way your team can sign in, turn on **Disable interactive sign-in. Only Google sign-in allowed.** on the **Google** tab. This blocks the email-code method for your organization, so everyone authenticates through Google.

<Warning>
  Before turning on **Disable interactive sign-in. Only Google sign-in allowed.**, confirm Google sign-in works for a test user. If Google sign-in becomes unavailable while enforcement is on, your team is locked out until you turn the toggle back off.
</Warning>

## Related content

<CardGroup cols={2}>
  <Card title="Sign-in, passkeys, and SSO" icon="key" href="/help/documentation/authentication">
    How every sign-in method works in Beebole, including the Single Sign-On panel and Custom OpenID.
  </Card>

  <Card title="Microsoft sign-in" icon="microsoft" href="/help/integrations/microsoft">
    Sign in to Beebole with a Microsoft account and require Microsoft sign-in.
  </Card>
</CardGroup>

## Frequently asked questions

<AccordionGroup>
  <Accordion title="Do I need to set anything up to sign in with Google?">
    No. Google sign-in is a built-in option on the Beebole sign-in screen — click the **Google** button under **Or Sign in with**. Linking your Google domains is optional and only adds organization-level controls such as automatic provisioning and Google-only sign-in.
  </Accordion>

  <Accordion title="Does Google sign-in create Beebole people automatically?">
    Only if you turn on **Automatically create new users on first SSO login** on the **Google** tab of the **Single Sign-On** panel. With that setting off, a person with a matching email must already exist in your Beebole account before they can sign in with Google.
  </Accordion>

  <Accordion title="What if my Google email is different from my Beebole email?">
    Beebole matches accounts by email address. If your Google email does not match the email on your Beebole profile, Google sign-in will not find your account. Make the two email addresses match, or contact [support@beebole.com](mailto:support@beebole.com).
  </Accordion>

  <Accordion title="Can I make Google the only way my team signs in?">
    Yes. On the **Google** tab of the **Single Sign-On** panel, turn on **Disable interactive sign-in. Only Google sign-in allowed.** This blocks the email-code method so everyone authenticates through Google. Confirm Google sign-in works for a test user first.
  </Accordion>

  <Accordion title="Where do I find the Google settings in Beebole?">
    Go to **Settings** > **Account Settings**, open the **Single Sign-On** panel, and select the **Google** tab. SSO is configured on the organization itself, not as a separate menu item, and all settings save automatically.
  </Accordion>
</AccordionGroup>