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

# Set up your own Gmail OAuth app (recommended)

> Connect Helium to your own Google Cloud OAuth app instead of waiting on Gravity's shared app's verification -- zero Google review needed for a Google Workspace org.

The fastest way to connect Gmail to Helium is to set up your **own** Google
Cloud OAuth app rather than waiting on Gravity's own shared app to clear
Google's verification review (which can take weeks). If your company uses
**Google Workspace**, you can register an "Internal" app that needs **zero
Google review, ever** — restricted to your own Workspace's members from the
moment you create it. This is the recommended path for any Workspace
customer, not a niche fallback.

**This page describes how to skip that wait today, not a permanent extra
step.** Once Gravity's own shared app completes Google's verification, the
plain **Connect Gmail** button on your dashboard will work directly for
everyone with no setup — nothing here forces a Workspace customer to keep
maintaining their own OAuth app afterward, though nothing forces switching
back either (see "Rotating your client secret" below).

If you're not on Google Workspace (a personal Gmail account only), skip this
— there is no "Internal" app option available to you, and Helium's own
shared app (once verified) is the only path. Leave the dashboard card blank
and Helium's shared app applies automatically. **In the meantime, while that
verification is still in progress**, you may see Google's "app isn't
verified" warning when connecting, or be unable to connect at all — contact
Gravity directly to be added to the interim test-user allowlist.

## Step-by-step (\~10 minutes)

These steps assume no prior Google Cloud experience. Google's own Console UI
can shift over time — if a menu label below doesn't match what you see, the
underlying steps (create project → configure consent screen → enable APIs →
create OAuth client) still apply.

1. **Create a Cloud project inside your Workspace organization.** Go to
   [console.cloud.google.com](https://console.cloud.google.com) signed in
   with your **Workspace** account — a personal non-Workspace account has no
   "Internal" user-type option at all, and Helium's code has no way to
   detect or enforce this ahead of time (Google's own org-membership check
   is invisible to the app). Click the project selector → **New Project**.
   Name it something recognizable (e.g. "Helium Integration").

2. **Configure the OAuth consent screen.** In the left nav: **APIs &
   Services → OAuth consent screen** (Google's newer UI may call this
   "Google Auth Platform → Branding/Audience"). Set:
   * **User Type: Internal** — the setting that skips Google's review
     entirely. If you don't see "Internal," your account isn't part of a
     Workspace organization.
   * App name, support email, and developer contact email: yours.

3. **Enable the APIs Helium needs.** In **APIs & Services → Library**,
   enable: **Gmail API** and **Google Calendar API**. Calendar access powers
   automatic [meeting-prep briefs](/helium/monitoring-and-discovery#calendar-meeting-prep-briefs)
   once Gmail is connected — there's no separate Calendar connect step.

4. **Create the OAuth client.** **APIs & Services → Credentials → Create
   Credentials → OAuth client ID**. Application type: **Web application**.
   Under **Authorized redirect URIs**, add the exact production callback URL
   (`https://lite.gravitygtm.com/api/helium/gmail/oauth/callback`) — getting
   this wrong produces a clear redirect-mismatch error, not a silent
   failure, so it's safe to try and fix.

5. **Copy the Client ID and Client Secret.** Google shows both once the
   client is created (you can view the Client ID again anytime, but not the
   secret — generate a new one from the same Credentials page if you lose
   it).

6. **Paste them into your dashboard.** Go to your
   [dashboard](https://lite.gravitygtm.com/dashboard) and fill in the
   "Your own Google OAuth app" card under the Helium section. The very next
   time you (or a teammate) click Connect/Reconnect Gmail, it uses your own
   app automatically — no deploy, no waiting.

## Rotating your client secret

Generate a new secret in Google Cloud Console and resubmit the SAME client
ID along with it on your dashboard — this replaces the stored value, it
doesn't create a duplicate. If you've already connected Gmail under this
client ID, rotating just the secret does **not** require reconnecting.
Submitting a genuinely **different** client ID does require reconnecting —
the dashboard will tell you when that's needed.

There is no self-serve "revert to Gravity's shared app" option yet — contact
Gravity directly if you need to switch back.