The notice appears in the green room, the screen where people check how they look and sound before clicking Join now. Admins can show it on every call or only when recording, transcription or Gemini note-taking is in use. It holds up to 350 characters of plain text plus an optional link to the full policy. Guests from outside your organization see the notice too, and it is the one set for the meeting host.

How the notice works

The green room is Google's pre-join screen, where people test their camera, microphone and speakers. When an admin turns the notice on, custom text and an optional link appear there, so people can review your rules on meeting recordings, transcripts and Gemini notes before they join.

The text goes in a field called Disclosure text and the policy address in Disclosure link. Google's setup page says the text is plain text only, up to 350 characters. You choose between two display options, covered below.

Google's announcement says the setting is off by default and is applied at the organizational unit level. Every user belongs to one unit, and a child unit inherits its parent's settings unless you override them. Google's pages do not say how the notice behaves on every way of joining, so test the ways your clients actually join.

Check availability first

Google lists Business Standard and Business Plus, Enterprise Standard and Plus, Frontline Plus, Education Fundamentals, Standard and Plus, and the Google AI Pro for Education add-on. Business Starter is not on the list. An extended rollout began November 2, 2026, and Google says the feature may take longer than 15 days to appear, so your Admin console may not show it yet.

The admin who sets it up needs the Google Meet administrator privilege. Google says end users have nothing to do.

Turn it on

Once the setting appears, an admin turns it on like this:

  • In the Google Admin console, go to Menu, then Apps, then Google Workspace, then Google Meet.
  • Click Meet safety settings.
  • To apply it to one department or team, select an organizational unit at the side.
  • Click Meeting disclosures and privacy.
  • Enter up to 350 characters in Disclosure text and, if you like, the address of your full policy in Disclosure link.
  • Choose "Always show" or "Only during recording, AI note-taking, or transcription."
  • Click Save, or Override for an organizational unit.

To go back to the inherited value, open the setting for that unit and click Inherit. To try the notice safely, create a test unit inside the unit your test accounts already belong to and move one or two accounts there. It inherits every other setting from its parent, so only the notice changes.

Google's notice page does not say when changes take effect. Its pages for related Meet settings say changes can take up to 24 hours and typically happen more quickly, so allow a day before you judge the result.

Find out what your meetings already create

Before writing a word, check what Meet is allowed to produce. Most of these settings sit in the Admin console under Apps, Google Workspace, Google Meet:

  • Under Meet video settings, whether Recording has "Let people record their meetings" checked.
  • Under Meet video settings, whether "Let users download and copy Meet recordings" is checked.
  • Under Meet video settings, what Meeting transcripts is set to.
  • Under Meet safety settings, whether Recording consent, Transcription consent or Take Notes with Gemini consent is set to "Require explicit consent."
  • In Google Vault, under Retention and then Settings, whether Meet is set to "Retained by Meet rule."

Google's transcription admin page says that on Business Standard you cannot turn transcription off in the Admin console. If that is your edition, the notice should assume transcripts are possible on any call.

Users and hosts can also have their own settings for recording, transcripts and notes, so check a few users' accounts as well as the console.

Know where meeting files go

Recordings, transcripts and Gemini notes are all saved in the meeting organizer's Google Drive, in a Google Meet folder with a sub-folder for each meeting. Google says that starting July 2026 the older Meet Recordings folder is renamed Legacy Meet Recordings and moved inside it, and old links keep working.

Recordings include the active speaker and anything presented. An email with the link goes to the organizer and the person who started the recording. A recording that starts at the scheduled time is linked to the Calendar event, and participants in the organizer's organization then get access automatically. Groups do not, so do not promise that everyone invited through a group gets a copy.

Gemini notes are saved the same way, and also attach to the Calendar event. Hosts and co-hosts use a Send notes to menu to pick "Hosts and co-hosts only," "Invited guests in my organization" or "All invited guests, including those outside of my organization." For instant meetings, notes go to the hosts and whoever started Take notes for me. Guests added through a group email must request individual access to the notes.

Copies are an easy gap to miss. Google's recording admin page says that starting April 30, 2026, people with Viewer or Commenter access to new recordings can copy and download them, and that recording owners can still restrict downloads for individual recordings. Check that setting before the notice says recordings stay in Drive.

Check retention before you promise a period

If you use Google Vault, Meet recordings follow your Drive retention rules unless you turn on Meet-specific retention, which is off by default. Google adds that meeting notes remain subject to Drive retention rules even after that, and so do copies you download and upload to Drive.

Order matters. Google warns that turning on Meet retention before you create Meet retention rules can leave some Meet data unprotected from deletion. It also warns that a badly configured rule can immediately and permanently delete recordings and logs, and it recommends testing new rules on a small set of accounts.

Not every edition includes Vault, and Google's Vault page does not say which do, so confirm yours. Without a retention rule, promise a period only if a named person deletes files on that schedule.

Write a notice that stays true

A good notice answers what a client wants to know before joining, so within 350 characters, try to cover:

  • What may be captured, such as recordings, transcripts or Gemini notes.
  • Where the files are saved and who gets them by default.
  • Who to contact about access, copies or deletion.
  • Where the full policy lives.

Leave out anything your settings cannot back up. "Everyone invited gets a copy" fails for group invitations, and "Deleted after 90 days" fails without a rule or a person doing it.

Put the detail on the linked page, including what is captured and when, how consent works, default sharing, retention and how to ask for a copy or deletion. Google says a Gemini summary can be incomplete, inaccurate or not generated, so name who checks notes before anyone relies on them. The link must open for people outside your organization, so use a page on your public website rather than a document only staff can open.

Choose when the notice shows

"Always show" suits most small offices, because everyone sees the same text whatever is running when they join. That includes calls where a host starts recording partway through. Google's pages do not say the notice reappears when a feature starts mid-meeting, though Meet does notify participants when a recording starts or stops.

The narrower option suits organizations that rarely record, transcribe or use Gemini notes. It only helps if the notice shows up when those features are actually running, so test it with a real scheduled and a real unscheduled call before you rely on it.

Pick "Always show" if any of these apply:

  • Hosts often start recording, transcripts or notes after the call begins.
  • Your edition cannot turn transcripts off, as Google says of Business Standard.
  • The notice covers more than capture, such as how to ask for a copy.
  • You want outside guests to see the same message on every call.

A notice is not consent

Nothing in Google's setup steps asks people to accept or acknowledge the notice. If your policy needs agreement before capture starts, Meet safety settings also include Recording consent, Transcription consent and Take Notes with Gemini consent. Each offers "Require explicit consent" or "Don't require explicit consent."

A separate setting called Streaming session consent denial action decides what happens when someone declines. Its options read "Allow users to quickly stop the artifacts on decline" and "Don't allow users to quickly stop the artifacts on decline." Google's page describes the settings only briefly, so test what a declining participant actually experiences before you describe it to staff.

Google says the consent settings apply only to mobile and web users, and people on Meet hardware or dialing in by phone are automatically consented. Changes can take up to 24 hours to apply. Whether you need consent at all is a legal question, so ask your attorney which rules apply to your calls, including calls with people in other states.

A worked example

Imagine a ten-person accounting office on Business Standard. Two partners record some client calls, staff use Gemini notes in internal meetings, and a few clients dial in by phone. This is a hypothetical office, not a description of any real client.

The admin's inventory shows recording allowed, transcripts that cannot be turned off on this edition, and no Vault rule. Because partners often start recording partway through a call, the office picks "Always show." It also requires explicit consent for recording and transcription.

The Disclosure text reads: "This meeting may be recorded, transcribed or summarized by Gemini. Files are saved in the organizer's Google Drive and shared with staff in the meeting. Clients may ask for a copy. To ask about access, copies or deletion, contact the office manager. Our full meeting policy is at the link." That is well under 350 characters. The Disclosure link goes to a page on the firm's public website, because a page behind the firm's sign-in would not open for clients.

The office has no Vault rule, so it makes no deletion promise in the notice. Instead the policy page says the office manager reviews recordings each quarter and removes old ones, and a calendar reminder makes that happen. The admin also checks "Let users download and copy Meet recordings" and tests a download with a viewer account, because a copy on a laptop would break any promise about where files stay.

Partners invite staff by name rather than through a group. Because phone callers are automatically consented, a partner tells phone participants aloud when recording starts. The admin applies everything to a test unit holding the office manager's account, waits a day, runs the checks below, then sets the same values at the top-level unit.

Common mistakes and how to spot them

Each of these makes a notice untrue, and each has a quick check:

  • Linking to a page only staff can open. Open the Disclosure link in a private window while signed out.
  • Promising copies to everyone invited. Invite a test group to a recorded test call and see whether a member can open the file.
  • Promising a deletion date nothing enforces. Find the Vault rule, or the person and reminder that do the deleting.
  • Setting the notice on one unit while hosts sit in another. Join test meetings hosted by someone in each unit.
  • Choosing the narrower option while hosts start features mid-call. Ask hosts how they usually start recordings and notes.

Test it before you tell staff

Wait a day after saving, then check:

  • Meeting disclosures and privacy shows your text in the Admin console.
  • A test user sees the notice in the green room and can open the full policy from it.
  • An outside guest using a personal Google account sees the host's notice, and the link opens for them.
  • With the narrower option, the notice appears for a call with notes or recording running and not for one with nothing running.
  • A two-minute test recording lands in the organizer's Google Meet folder, and its sharing settings show who can open it.
  • A Gemini notes test, in a meeting of at least 15 minutes as Google recommends, reaches only the recipients you chose.
  • If consent is on, a web user and a mobile user each get the prompt.

What to do this week

  • Confirm your edition is on Google's list and see whether Meeting disclosures and privacy appears yet.
  • Run the settings inventory and write down what each setting is today.
  • Name one person who owns the meeting policy, and publish the full policy on your public website.
  • Write the notice, turn it on for a test unit, run the checks, then roll it out to everyone.
  • Tell staff what the notice says, what it does not do, and who to ask.

Short answers to common questions

Your notice travels with your hosts. Google says guests see the notice set for the meeting host, so when staff join another organization's call, that host's notice applies, not yours.

The notice changes nothing about access. Who can open a file still depends on the organizer's Drive, the Calendar attachment rules and the Send notes to choice.

Meet keeps its own signals. Participants are notified when recording starts or stops, and a pencil icon appears while Gemini takes notes.

Where ALCO can help

ALCO's Google Workspace service covers Gmail, Drive, Calendar and the admin console, run by people who answer, and ALCO also offers user training for staff. The ALCO help desk is staffed 24 hours a day, including holidays, and calls are answered by a person.

Sources