Google Meet support

Last updated date:

Connect, reconnect, and troubleshoot Google Meet 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.
  • Enable meetings.space.readonly in the approved parent scope contract and confirm the delegated user can access the intended conferences.
  • Run synchronization within Google's 30-day structured-transcript availability window when transcripts are required.
  • Do not send Google Meet credentials, customer content, personal information, or private record data by email or through an ordinary support ticket.
Google Meet authorizationGoogle Meet REST API authorization guidance.

2. Connect Google Meet

  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 meetings.space.readonly in the parent domain-wide delegation or Marketplace scope grant.
  4. Confirm the delegated administrator or eligible user can read the intended conference records and artifacts.
  5. Confirm the Google Meet child source appears beneath the verified Google customer connection and completes its first synchronization.

3. Authorization and connection problems

Meet child not provisioned
Confirm the Google Workspace parent is active for the whole customer, meetings.space.readonly is granted, and the eligible delegated user is covered.
Transcript absent
Confirm a structured transcript was generated and synchronize before Google's 30-day availability window expires. A recording does not guarantee a transcript artifact.
Recording unavailable
Seedling intentionally synchronizes recording metadata, not recording bytes. Do not add Drive or Meet write permissions to retrieve media.

4. Missing or delayed data

  1. Confirm the conference and artifact are visible to the delegated Google user and that meetings.space.readonly remains granted.
  2. Check conference end time, transcript generation state, the 30-day transcript window, participant identity mapping, and provider retry warnings.
  3. Confirm current provider evidence maps the conference audience 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. Rotate or replace the Google Workspace parent authorization without creating a separate child credential.
  2. Retain meetings.space.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.