Google Drive support

Last updated date:

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

1. Before you start

  • Choose the Google identity and Seedling personal or workspace scope, or use the verified Google Workspace parent for organization-wide coverage.
  • For a dedicated connection, request drive.readonly with offline access through a configured Google OAuth web client.
  • Confirm the identity can natively open each selected file or shared drive; do not broaden Google sharing for Seedling alone.
  • Do not send Google Drive credentials, customer content, personal information, or private record data by email or through an ordinary support ticket.
Google Drive API scopesGoogle's Drive API authorization scope guidance.

2. Connect Google Drive

  1. In Seedling, open Connections and choose Google Drive.
  2. Choose personal or workspace scope; actor-owned Drive content remains owner-only in human-facing Seedling surfaces.
  3. Enter the Google access token and refresh token for the intended identity.
  4. Connect and verify the Google identity before the first Drive change scan completes.
  5. Inspect a private and a shared file to confirm projected audiences fail closed and match provider evidence.

3. Authorization and connection problems

Drive scope rejected
Repeat authorization with drive.readonly and offline access. Seedling does not request a write scope to compensate for an inaccessible file.
File forbidden or missing
Confirm the authorized Google identity can open the exact file and that it was not moved, trashed, link-restricted, or removed from a shared drive.
Audience is empty
Check stable principal mapping and current provider permission evidence. Seedling intentionally grants no human audience when Drive ACL evidence is incomplete or ambiguous.

4. Missing or delayed data

  1. Confirm the file is visible to the authorized identity and is not a shortcut to an inaccessible target.
  2. Check shared-drive membership, file permissions, export support, MIME type, change-token continuity, and provider retry warnings.
  3. For a human read, confirm Drive returned current permission evidence that maps to an active Seedling 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. Authorize the same Google identity again with drive.readonly and offline access.
  2. Replace the access and refresh tokens on the exact Drive connection and confirm its immutable provider identity.
  3. After a successful change scan, revoke the previous Google authorization.