Google

Register a Google OAuth app for your app name

You are setting up the Google app that your business will use to connect its own Google accounts to Meg Secrets. Console labels change over time; follow the intent of each step. Stop at every [person] step and ask the owner to do it.

Values you will need

• Redirect URI: https://secrets.getmeg.ai/connections/callback
• Scopes: openid email
• App name: your app name

Steps

1. [person] Sign in at https://console.cloud.google.com with an admin of the business's Google account. Accept the Google Cloud terms if asked (the owner must do this).
2. Create a project named your app name, or pick the business's existing one.
3. Enable each API the scopes need (for example the Gmail API or Google Calendar API) under APIs & Services → Library.
4. Open Google Auth Platform → Branding (older consoles: OAuth consent screen). Set the app name, a support email, and the business's privacy policy URL.
5. Under Audience, choose:

• Internal if every user who will connect belongs to the business's own Google Workspace. Internal apps skip Google's verification review. This is the right choice for a business connecting its own accounts.
• External only if outside users must connect. Sensitive scopes then need Google's verification, and restricted scopes (such as full Gmail access) need a yearly third-party security assessment.

1. Under Data access, add the scopes openid email.
2. Under Clients, create an OAuth client of type Web application and add https://secrets.getmeg.ai/connections/callback as an authorized redirect URI.
3. Copy the Client ID and Client secret.
4. [person] The owner pastes them at your workspace Settings → Sign-in apps. Never put the client secret in a chat message or a file.
5. If the audience is External and sensitive scopes are used: [person] the owner submits the app for verification and answers Google's reviewers.

Check

After saving, the owner clicks Connect Google in Meg Secrets and signs in. The connection should show as active.