Choosing a Meeting-Capture Path

Two sources ingest Gemini meeting notes, and they overlap:

• The Google Meet source reads transcripts through the Meet API, fanning out across your Workspace members.
• The Google Drive source reads whatever files land in one Drive folder — including the Docs that Gemini writes for a meeting.

Point both at the same organization and the same transcript can be ingested twice, under two different entity types. This page explains what each path actually captures, what governs its footprint, and how to choose.

The note-taking gate

The single most important thing to understand: capture scope is set upstream of Corveil, by your Gemini note-taking policy — not by source configuration.

A Google Meet call held without note-taking or transcription enabled produces nothing for either source to find. There is no transcript, no meeting metadata, and no attendee list. The Meet connector checks for a usable transcript before it emits anything, and a meeting that has none is skipped entirely rather than recorded as an empty meeting.

This has two consequences that surprise people in opposite directions:

If your team turns note-taking on deliberately, per meeting, then the Meet source's org-wide fan-out ingests exactly the meetings you chose to transcribe — and nothing else. The meeting-level opt-in is the privacy control. Enabling the source org-wide does not sweep up untranscribed conversations, because those conversations left no artifact to sweep.

If your Workspace has Gemini note-taking on by default, the same source with the same configuration ingests a great deal more. Nothing in Corveil changed; your note-taking policy did.

Same source, same config, completely different footprint. Settle the note-taking policy first — it is the decision that determines what gets captured.

Check this before you scope anything

Look at your Workspace's Gemini / "take notes for me" defaults in the Admin console before tuning source config. Source-side scoping (below) narrows what Corveil reads; it cannot narrow what Google already wrote down.

Diagram B — the two paths

Both paths hang off the same gate:

In words: the "No" branch is the point. Whether a meeting is transcribed at all is a policy decision made in Google Workspace, upstream of Corveil, and it governs both sources equally. Everything below that gate is a question of which path reads the resulting Doc — the Meet API across all members, or one watched Drive folder.

Side by side

	Meet path	Drive path
Reads	Meet API transcripts, titles, participants	Any file under one Drive folder — Gemini notes among them
Creates	Meeting entities	Document entities keyed on the Drive file id
Coverage	Every Workspace member, by impersonation	One folder, on one Drive
Multi-organizer	Yes — fans out, so it catches meetings organized by anyone	No — misses any organizer whose notes land elsewhere
Attendees	Structured participant list; emails with directory_subject	Whatever the Doc body happens to contain
Footprint governed by	Your note-taking policy, then member_allowlist / workspace_domains	Your note-taking policy, then which folder you watch
Curation	None — if it was transcribed and in scope, it is ingested	Full — a human decides what goes in the folder
Non-Meet sources	No	Yes — anything dropped in the folder, including manual uploads
Requires	Service account with domain-wide delegation	Read access to one folder

Which to choose

For an organization that transcribes deliberately, the Meet source is usually the better choice. This is the opposite of the intuition most people start with, so it is worth spelling out:

1. The privacy work is already done by the meeting-level opt-in. Choosing Drive to avoid over-capture buys you protection you already had.
2. Meet gives multi-organizer coverage for free. A single folder_id does not — see below.
3. You get structured participants instead of whatever the Doc body contains.

Choose the Drive path when one of these is true:

• You want to curate what gets ingested after the fact — a human moves selected notes into the watched folder, and only those are read.
• Notes come from somewhere other than Google Meet. Dropping a transcript from any source into the watched folder ingests it; this is the simplest manual-upload pattern Corveil supports.
• You cannot get domain-wide delegation approved, but you can get read access to one folder.

Running both is legitimate — Meet for automatic coverage, Drive for manual uploads from other sources. Be aware that the two paths land the same transcript as different entities: the Meet source creates a Meeting (with structured attendees), while the Drive source creates a document entity keyed on the Drive file id. A meeting whose notes also sit in the watched folder therefore appears in the graph twice, in two shapes, rather than being deduplicated into one record. If you do not want that, point the Drive folder somewhere Gemini does not write to.

The per-organizer Drive problem

If you choose the Drive path, this is the failure mode to plan around.

Gemini writes meeting notes into the organizer's own My Drive. Not a shared location, not a per-org folder — the Drive of whoever scheduled the meeting.

The Drive source takes a single folder_id. So pointing it at one person's meeting-notes folder captures that person's meetings and silently misses every meeting organized by anyone else. There is no error and no warning: the source is working correctly, reading the folder you named, which simply does not contain other people's notes.

This gap is easy to miss in a pilot. One person schedules the standups, their notes land in their My Drive, the source reads them, everything looks right. It stays right until a second person schedules a meeting.

The fix is a Shared Drive. Create one, have organizers save or move meeting notes into it, and point the source at a folder there. See Shared (Team) Drives on the Drive source page for the membership step this needs — a service account must be a member of the drive, not just have the folder shared with it.

A single My Drive folder is a single-organizer solution

If more than one person in your org schedules meetings you care about, one folder_id pointed at a My Drive will under-capture, quietly. Either use a Shared Drive or use the Meet source.

Scoping the Meet source

The Meet source fans out across every org member by default. Two config fields narrow that, and both are supported production configurations — not just pilot-phase training wheels:

Key	Effect
member_allowlist	Comma-separated Workspace users. Fan-out is restricted to exactly these members.
workspace_domains	Comma-separated domains. Only members whose email domain matches are impersonated; everyone else is skipped.

Use member_allowlist to capture one team's meetings and no one else's — a standing configuration, not a temporary one. Use workspace_domains in a multi-domain Workspace to keep capture inside the domain that consented to it.

Both narrow which members Corveil impersonates. Neither can reach a meeting that was never transcribed, and neither is needed to prevent that — the note-taking gate already handles it.

Deciding in one pass

1. Settle the note-taking policy first. It sets the ceiling on what either source can capture.
2. Transcribing deliberately, want automatic coverage? Meet source. Add member_allowlist or workspace_domains if you want a narrower slice.
3. Want a human to curate, or ingesting notes from outside Meet? Drive source, pointed at a Shared Drive folder.
4. More than one meeting organizer, and you picked Drive? It must be a Shared Drive, or you will under-capture without noticing.

Related

• Google Meet source — setup, config fields, DWD
• Google Drive source — setup, Shared Drives, troubleshooting
• Google Calendar source — scheduled events and attendees, on the same credential, whether or not a meeting was transcribed