1. Overview
The implemented Google Meet source is an organization-level child of the Google Workspace connection. It uses short-lived delegated tokens to read conference records and artifacts visible to the delegated user.
Seedling does not download recording bytes. Google exposes structured transcript entries for only 30 days after a conference ends, so transcript synchronization must run inside that provider retention window.
2. Connection and scope
Seedling verifies the provider account before storing the workspace connection. A current Seedling workspace administrator controls installation and disconnect; account identity is never inferred from an email address or display name.
- Google Workspace parent connection
- This source is created beneath a verified organization-wide Google Workspace Marketplace or customer-managed service-account connection. It has no separate child credential or personal connection form.
- Connection ownership
- This connector is workspace-only. A current Seedling workspace administrator controls installation, credential replacement, disconnect, and purge for the exact connection.
3. Google Meet data Seedling accesses
Seedling uses synchronized information for source-backed search, operating context, verification, and customer-approved workflows. Availability depends on the connected account, selected resources, provider plan, and native permissions.
- Conferences
- Conference spaces, start and end times, meeting codes, lifecycle state, and relationships to Workspace identities.
- Attendance
- Participants, participant sessions, join and leave timing, and provider identity context returned to the delegated user.
- Artifacts
- Recording metadata and structured transcript entries when available; recording media bytes are excluded.
4. Read-only permission contract
Meet uses the read-only Google Workspace meetings.space.readonly scope. It cannot start, configure, record, admit, message, or end a meeting.
- meetings.space.readonly — read conference records, participants, participant sessions, artifact metadata, and structured transcript entries visible to the delegated user.
- No recording download, Meet settings, or meeting mutation scope is requested.
- Directory read scopes on the parent resolve stable Workspace principals; they do not grant Meet content by themselves.
5. Security and access
- Provider credentials and other connection secrets are encrypted in the workspace tenant data plane, never returned to the browser, and excluded from logs and queue payloads.
- Every source, synchronization, secret lookup, audience contribution, disconnect, and purge remains bound to the exact connection that created it.
- Workspace connections use provider-returned object permissions and stable principals for human audience projection. Missing, stale, ambiguous, or unmappable ACL evidence contributes no human audience, and no Seedling administrator or steward may broaden it.
- Meet audience projection uses provider-returned organizer, participant, artifact, and stable-principal evidence. Missing or unmappable evidence contributes no human audience, including for administrators and stewards.
- Generated output cannot bypass Seedling's human review, verification, and approval gates.
6. Retention and deletion
- Connected data
- Synchronized Google Meet records remain while the connection is active and are removed through a durable integration purge after disconnect.
- Credentials
- Stored Google Meet credentials or connection secrets and connection-owned synchronization state are deleted from active Seedling systems as part of the purge.
- Backups
- Deleted information may remain in encrypted, access-restricted backups until expiry, ordinarily within 35 days after active-system deletion.