Gmail support

Last updated date:

Connect, reconnect, and troubleshoot Gmail without sharing credentials or customer content through support channels.

1. Before you start

  • Choose the Google mailbox and Seedling personal or workspace scope deliberately.
  • Create or select a Google OAuth web client, configure its redirect URI and consent screen, and request offline access.
  • Authorize exactly openid, email, profile, and gmail.readonly; do not add Gmail write or send scopes.
  • Do not send Gmail credentials, customer content, personal information, or private record data by email or through an ordinary support ticket.
Gmail API scopesGoogle's Gmail API authorization scope reference.

2. Connect Gmail

  1. In Seedling, open Connections and choose Gmail.
  2. Choose personal or workspace scope; personal Gmail remains actor-owned and cannot be promoted into workspace access.
  3. Enter the access token and refresh token returned by the Google authorization-code flow.
  4. Connect and confirm the verified mailbox identity before the first synchronization completes.
  5. Verify that mailbox objects appear only for members supported by projected Google permission evidence.

3. Authorization and connection problems

Refresh token missing or rejected
Repeat the authorization-code flow with access_type=offline and explicit consent for the intended Google user, then replace both tokens on the exact connection.
Insufficient Gmail scope
Grant gmail.readonly. Seedling does not accept a write scope as a substitute and treats a forbidden mailbox as unavailable rather than empty.
Member cannot read a message
Check the connection owner and projected Gmail audience evidence. Workspace membership, administration, and source stewardship do not grant a raw-message bypass.

4. Missing or delayed data

  1. Confirm the authorized Google user can open the message, thread, label, or attachment in Gmail.
  2. Check Gmail history continuity, label filters, attachment availability, and any provider retry warning.
  3. For a human read, confirm the reader maps to a stable principal supported by the object's projected audience evidence.
  4. Allow incremental synchronization and provider retry handling to complete. A temporary provider failure does not delete previously synchronized data.
  5. If the issue remains, contact support@tryseedling.ai with the Seedling workspace, safe timestamps, and non-sensitive provider record identifiers. Do not include credentials or record contents.

5. Rotate or replace access

Never use email or an ordinary support ticket to transfer the old or replacement credential.

  1. Complete a fresh Google OAuth authorization-code flow for the same mailbox with gmail.readonly and offline access.
  2. Replace both tokens on the exact Gmail connection and confirm the same Google identity.
  3. After synchronization succeeds, revoke the old Google authorization or token grant.