Google Sheets support

Last updated date:

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

1. Before you start

  • Complete the Google Workspace organization-wide launch gates: whole-customer installation, verified customer identity, exact read-only scopes, and eligible-user coverage.
  • Keep drive.readonly in the parent authorization and confirm the delegated users can natively open the intended spreadsheets.
  • Review connector bounds for displayed values and formulas; Seedling does not treat Sheets as an unrestricted warehouse extraction path.
  • Do not send Google Sheets credentials, customer content, personal information, or private record data by email or through an ordinary support ticket.

2. Connect Google Sheets

  1. In Seedling, open Connections and select Google Workspace as a current workspace administrator.
  2. Install the Marketplace app for the entire organization or configure customer-managed domain-wide delegation; partial OU or group installation is not supported.
  3. Include drive.readonly in the parent domain-wide delegation or Marketplace authorization.
  4. Confirm the intended spreadsheet population is visible through Drive and retains current native permission evidence.
  5. Confirm the Google Sheets child source appears beneath the verified Google customer connection and completes its first synchronization.

3. Authorization and connection problems

Sheets child not provisioned
Confirm the Google Workspace parent is active, drive.readonly remains granted, and the spreadsheet is visible to a covered delegated user.
Cells or formulas missing
Check sheet dimensions, connector bounds, protected or unsupported content, and whether the authorized identity can open the exact spreadsheet.
Audience is empty
Inspect current Drive permission evidence and stable-principal mapping. Seedling intentionally fails closed rather than granting stewards spreadsheet content.

4. Missing or delayed data

  1. Confirm the spreadsheet is visible to a covered delegated user through Drive and has not been trashed or moved outside the authorized population.
  2. Check Drive change continuity, sheet bounds, supported cell content, native permissions, and provider retry warnings.
  3. Confirm the spreadsheet's Drive ACL evidence maps to the requesting active member.
  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. Rotate or replace the Google Workspace parent authorization without creating a separate child credential.
  2. Retain drive.readonly and whole-organization coverage on the replacement parent authorization.
  3. Verify the same immutable Google customer identity before retiring the previous Marketplace authorization or service-account credential.