AI meeting notes can now start automatically. Who gets the record?

For some Google Workspace customers, meeting notes are becoming something that starts unless someone changes the setting.

Google’s administrator documentation says that on or after September 21, 2026, Business Standard and Business Plus organizations get automatic note-taking enabled by default for meetings with three or more guests, including the host. Required Gemini and smart-feature settings still matter. Administrators can opt out, and users can override the default in their own Meet settings. The help page was updated September 24. [1]

For the affected meetings, the default changes the question participants need to ask. Alongside “Is anyone taking notes?” comes “Which artifact is being created, who receives it, and how long does it remain?”

We followed the documented paths in Google Meet, Microsoft Teams and Granola to map what survives after the call.

A meeting can leave several different artifacts

Audio, a transcript and a summary are not interchangeable.

Audio preserves a recording. A transcript represents speech as text, including recognition errors or speaker-assignment problems. A summary selects and rewrites information. A product can avoid retaining audio while still storing the transcript and notes used to create a useful record.

Granola’s security documentation makes that distinction explicit. It says desktop audio is not stored, while mobile can cache audio temporarily for transcription; transcripts and notes are retained. It also names cloud transcription and AI providers. Claims about those providers not training on data are separate from Granola’s own model-improvement controls. [2]

A buyer looking for “no recordings” should therefore ask a second question about text artifacts. Removing one form of data does not answer where the other forms go.

Follow the file after the meeting

The meeting-record map links each documented behavior to its source.

Invited can mean more than attended

Google’s note-sharing options include different audiences, such as invitees, organization invitees or hosts. That means the list of people who can receive notes need not be identical to the people visible in the call. The organizer’s document and sharing settings deserve an explicit check. [3]

Consider a recurring project meeting with an old invitee list. A useful pre-meeting check is whether everyone on that list still belongs in the information flow. The selected sharing audience determines which invitees receive access.

For a sensitive conversation, agree on the record and intended audience before using automated notes. Follow the organization’s rules and the participants’ expectations. This article is not a substitute for legal advice about recording or for an employer’s retention policy.

Which policy controls a meeting record?

Microsoft documents a default 120-day expiration for Teams recordings and transcripts, with administrator configuration available. It also warns that automatic expiration is not a compliance-retention solution. Other policies and storage behavior can affect what happens to the files. [5]

It is therefore misleading to promise that every Teams meeting record disappears after exactly 120 days. The number is a setting to inspect, not a universal deletion guarantee. It also does not automatically describe a separately copied summary, an exported document or another participant’s authorized record.

Our practical recommendation is to keep a short artifact inventory: recording, transcript, generated notes, shared document and exported copy. For each one, record its owner, audience and removal rule. That inventory is more useful than a single “we delete recordings” sentence.

Summaries need a correction path

A summary can turn an exploratory discussion into a confident-looking decision. Before using it as a record of commitments, check the action, owner, deadline and any condition attached to it.

An illustrative example: “We could send the revised draft Friday if the research is complete” should not become “Research team will deliver Friday” without confirmation. That difference can survive in a shared note long after everyone forgets the wording of the call.

A useful workflow makes correction visible. Let participants identify an incorrect decision or attribution, establish who owns the final record and distinguish the approved version from an automatically generated draft. Decide who owns those checks before the notes become a working record.

When an answer later relies on those notes, retain the distinction between the note and the original exchange. Our AI citation-check article explains how to test the connection between a claim and its source.

The next default to review is yours

For an organizer, three questions can make the new convenience easier to manage: will notes start automatically for this meeting, who will receive them, and which record should people rely on afterward?

For a participant, ask what is being captured and raise concerns before sensitive material is discussed. For an administrator, inspect actual tenant settings rather than inferring them from a general announcement.

A well-kept meeting record can preserve decisions and help people who need context. Its value depends on the record being accurate, findable and shared with the right audience. The automated start is only the beginning of that lifecycle.

Method and dates

We reviewed official documentation through 28 September 2026. The Google default-change page is newly updated September 24; the other pages describe current documented behavior with different update histories. We did not join meetings, enable recording, test deletion or measure summary accuracy. Vendor retention statements are not independent security findings. Kluro publishes this analysis; any imported meeting context remains subject to source access and the user’s permissions.