As an indie developer who also takes on client site work, I had decided to try Meet's automatic notes on a weekly check-in with a client's office coordinator. Once the call was running, I went looking for the sharing option and could not find it anywhere on the screen.
My first assumption was that I had simply forgotten where the setting lived. Rereading the help page showed me it was not a matter of where to look but of when. Some settings are locked once anyone has joined, and the place to decide them is the calendar event, not the meeting.
Notes are something you set up in the event, not something you ask for in the call. Since I started working that way, the last five minutes before a meeting have stopped being a scramble.
What follows is what I settle before a meeting when a small team or an office role starts using it: language, sharing scope, how notes start, and what to say to participants.
Check the organizer's side first, not the feature
"Take notes for me" writes the content of a Meet call into a Google Doc. Whether you can use it depends on the organizer's plan.
According to Google's help page, it requires an eligible Google Workspace edition or a Google AI plan. The same page lists the supported languages — English, French, German, Italian, Japanese, Korean, Portuguese and Spanish — and says one meeting supports only one language. A call that mixes Japanese and English is not covered at the moment.
Length matters too. A second help page recommends meetings between 15 minutes and 8 hours, and says summaries can be missing for shorter ones. If you try it on a five-minute stand-up and nothing appears, that may not be a fault.
My order of checks:
- Is the organizer's account on an eligible edition or Google AI plan?
- Will the call be held in one of the supported languages?
- Is the meeting likely to run at least 15 minutes?
If a coordinator is the organizer, check from their account. Some organizations have it switched on by an admin already, so whether the option shows on your own screen is the most reliable answer. If it does not, this note on telling a rollout delay from a real fault may help.
Decide: per event, or for everything
There are two ways to turn notes on.
| Method | Where | Good for |
|---|---|---|
| Per event | Open the event in Google Calendar, add Google Meet, open "Video call options", and under "Meeting records" tick "Take notes with Gemini" and pick a language | Only recurring check-ins need notes; language or sharing differs by meeting |
| For all meetings | meet.google.com settings, "Meeting records", then "Automatic note taking for all future meetings": Off, all scheduled meetings I host, or all scheduled meetings I host with 3+ guests | Most meetings you host should have notes |
I first reasoned that setting everything to automatic would be easiest. Then it struck me that even a short two-person call would become a recorded one, and I did not like that surprise later. I now use the "3+ guests" option and add one-to-one calls per event, only when I want notes.
The help page has one important caution: once someone has joined the call, you can't change the notes or transcription settings. The pre-join screen shows whether notes will be on, so that screen is your last chance to check.
A single line in the event description makes the setup easy to hand over:
[Notes] Take notes with Gemini: on / Language: Japanese / Sharing: invited guests in my organization onlyThe line exists for the day the person who set it up and the person hosting are different. Calendar events change hands more often than you would expect.
Narrow the sharing scope when even one outside guest is invited
The event's "Take notes for me sharing default settings" offers three choices.
| Choice | Who receives the notes | When I use it |
|---|---|---|
| All invited guests, including outside my organization | Everyone on the invite | A joint project where sharing with everyone is the plan |
| Invited guests in my organization | Only people in the same organization | Internal check-ins |
| Hosts and co-hosts only | A few people on the host side | Meetings with a client; I want to review before forwarding |
The help page on how participants are informed has three details that are easy to miss.
- "Invited guests" means everyone on the calendar invite, not only those who attended. Someone who declined still receives the notes.
- Guests invited through a group email address must request access to the doc individually.
- External guests can see the notes attachment on the event, but that alone doesn't open the doc.
When even one client is on the call, I start from "Hosts and co-hosts only", fix names and figures, and forward the notes myself. It is the same instinct as deciding where a Gem is blocked before asking anyone: opening things up is safer after you've checked.
Don't leave the heads-up to the icon
Meet tells participants that notes are being taken. According to the help page, a pencil icon appears on every participant's screen, and where an admin requires consent, buttons such as "Start", "Join", "Continue" or "Leave" appear.
Still, a small icon disappears from view once the call begins, and someone sharing slides often won't look at it. So I also say a sentence aloud at the start:
We're taking notes with Gemini today. They'll stay inside our team for now. If that's a problem, please tell me before we begin.
A reseller's 2026 explainer from TokyoScaler likewise recommends announcing it at the start of meetings that include outsiders and keeping the sharing scope internal. Since it is a vendor's article, I did not rely on its price comparisons, but its operating rules don't conflict with the help pages.
One more detail from the help page: screenshots are used only when a presentation stays on screen for at least 10 seconds. If a slide shows personal data, close it before you share.
Read the notes once, as a draft
After the meeting, the organizer receives an email with a link to the summary, and the same link appears on the calendar event. The doc is saved in the organizer's Drive, in a "Google Meet" folder, with two tabs: "Quick notes" and "Full notes".
The help pages themselves say summaries may be incomplete or missing depending on connection quality and meeting length. So I treat what arrives as a rough draft and check three things:
- Spelling of people's names and company names
- Amounts, dates and quantities
- Who owns what, and by when
Only after fixing those do I widen the sharing scope. That order has kept wrong figures from reaching people outside the team.
The smallest first step is to pick one recurring meeting next week and paste the one-line note into its event. Say a sentence at the start, and read the three items afterward. I eased into it the same way, starting with a standing check-in on a client project.
If you are also thinking about in-person meetings, how to decide where those notes land is covered in designing the Drive destination for Meet notes.