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

# Allow Starbridge to connect Gmail inboxes

> Configure Google Workspace app access so your team can connect their Gmail inboxes to Starbridge Sequences.

<Note>
  Inbox connection is only used for sending Sequences directly from Starbridge. See [Connect your inbox](/sequences/connect-your-inbox) for the full workflow.
</Note>

<Tip>
  If you get a message that "This app is blocked" when trying to connect your Gmail inbox to Starbridge, this article may help.
</Tip>

If your team sends Sequences from Gmail, a Google Workspace administrator will need to first approve Starbridge in the Admin console.

This is a one-time setup. Once Starbridge is approved for your Google Workspace, every user can connect their own inbox without any further admin involvement, including users on other domains inside the same Google Workspace.

## Before you start

You need a **super administrator** account, or an account with the **Service Settings** administrator privilege, in the Google Admin console. If you don't manage Google Workspace yourself, forward this page to whoever does.

You'll also need Starbridge's OAuth client ID:

<CodeGroup>
  ```text Starbridge OAuth client ID theme={null}
  157602306522-31ucodglp1a50kke0oh32jr49ibcqqt8.apps.googleusercontent.com
  ```
</CodeGroup>

## Approve Starbridge in the Admin console

<Steps>
  <Step title="Open API controls">
    Sign in to the [Google Admin console](https://admin.google.com) and go to **Security → Access and data control → API controls**.
  </Step>

  <Step title="Open app access control">
    Under **App access control**, click **Manage Third-Party App Access**, then click **Configure new app**.
  </Step>

  <Step title="Find Starbridge by client ID">
    Choose **OAuth App Name Or Client ID**, paste the Starbridge client ID from above, and press Enter.  

    Select the Starbridge result, then select the specific client ID shown on the next screen and click **Select**.
  </Step>

  <Step title="Choose which organizational units get access">
    Select the organizational units (OUs) whose users need to connect inboxes. If you're not sure, apply the setting to your top-level organization so every user in the Workspace is covered. This is the most common choice.

    <Tip>
      If you scope access to specific OUs, note which ones. When a rep reports that their inbox won't connect, check whether the OU their account lives in has access to Starbridge.
    </Tip>
  </Step>

  <Step title="Set access to Trusted and finish">
    Select **Trusted**, review your selections, and confirm.

    Starbridge now appears in your list of configured apps. Changes can take up to 24 hours to propagate, though they usually apply sooner.
  </Step>
</Steps>

## Connect an inbox

Once Starbridge is approved, any user can connect their own inbox from **Settings → Email connections**, and admins can connect inboxes for the whole org from **Settings → Integrations**. Builders can also connect an inbox directly from a Sequence. See [Connect your inbox](/sequences/connect-your-inbox) for all three paths.

At the Google consent screen, the user picks the account they want to connect and clicks **Continue**, then **Allow**. If the account they want isn't listed, they should click **Use another account** and sign in with it directly.

## Troubleshooting

<AccordionGroup>
  <Accordion title="Access blocked: authorization error, or Error 400: admin_policy_enforced">
    This is the standard signal that Starbridge hasn't been approved for the user's account. Work through these in order:

    1. **Confirm Starbridge is configured at all.** In **Security → Access and data control → API controls → Manage Third-Party App Access**, search for the Starbridge client ID. If nothing comes back, complete the steps above.
    2. **Check the organizational unit.** Open the Starbridge entry and click **View details** to see which OUs are covered. If the user's account sits in an OU that isn't listed, click **Change access**, add that OU, and grant access again.
    3. **Check the access level.** If Starbridge is set to **Limited** or **Blocked** or **Specific Google data**, change it to **Trusted**.
    4. **Check the unconfigured-apps default.** If your Workspace is set to *Don't allow users to access any third-party apps*, apps must be explicitly approved — which is what the steps above do. Confirm the change saved.
    5. **Retry after the change propagates.** Have the user sign out of Google entirely, or open an incognito window, sign in to Starbridge, and try connecting again.
  </Accordion>

  <Accordion title="The user is on a different Google Workspace">
    A rep whose email lives on a second Workspace — a subsidiary, an acquired company, or a separate sending domain — needs Starbridge approved in *that* Workspace's Admin console too. Approval doesn't carry across Workspaces. Additional domains inside the *same* Workspace are covered automatically.
  </Accordion>

  <Accordion title="The user sees a screen asking them to request access">
    Some Workspaces are configured to let users request access to unconfigured apps instead of blocking outright. If a rep submits a request, it lands in **API controls → Apps pending review**, where an admin can approve it — this reaches the same end state as configuring the app manually.
  </Accordion>

  <Accordion title="Nothing here fixed it">
    Contact your GTME or [support@starbridge.ai](mailto:support@starbridge.ai).
  </Accordion>
</AccordionGroup>

## Next steps

<Columns cols={2}>
  <Card title="Connect your inbox" icon="paper-plane" href="/sequences/connect-your-inbox">
    Connect Gmail or Outlook, and send Sequences from your own inbox.
  </Card>

  <Card title="Integrations overview" icon="plug" href="/integrations/integrations-overview">
    Connect Starbridge to your CRM, Slack, and the rest of your stack.
  </Card>
</Columns>