How to block AI notetakers from your meetings (Zoom, Teams, Meet)
The exact settings that keep uninvited notetaker bots out of your calls, per platform, host and admin.
In this article
- Why are AI notetaker bots suddenly everywhere?
- How do I block AI notetakers in Zoom?
- How do I block AI notetakers in Microsoft Teams?
- How do I block AI notetakers in Google Meet?
- Why does Otter (or Fireflies) keep joining after I removed it?
- IT admins: how do you block AI notetakers org-wide?
- Can attendees block someone else's notetaker bot?
- Is there a way to get notes without policing bots at all?
To block AI notetakers from a meeting, control who is admitted at the door and who can install the app in the first place: enable a waiting room and admit manually, turn off host-side AI transcription, and (the durable fix) have your IT admin restrict the third-party apps and bot accounts allowed into your Zoom, Microsoft Teams, or Google Meet tenant.
Why are AI notetaker bots suddenly everywhere?
A notetaker bot is a headless participant that a colleague (or their calendar assistant) sends into your call to record and transcribe it. Because it connects like any other guest, it shows up in the participant list with a name like "Otter.ai", "Fireflies.ai Notetaker", or "Read.ai", and unlike a human, it never leaves on its own. The question is common enough that Zoom now has a dedicated community thread for it.
How do I disable AI Notetakers (otter.ai, read.ai, fireflies.ai, etc.) from joining our meetings?
University IT desks field the same question at scale. The University of Illinois and UW-Madison both publish knowledge-base articles walking staff and faculty through removing and blocking notetaker bots, and consumer-security vendor Bitdefender published a guide after a wave of reports that Otter kept joining meetings uninvited. The steps below consolidate what those sources recommend, per platform.
How do I block AI notetakers in Zoom?
Zoom gives you two layers: what you, the host, can do in a single meeting, and what a Zoom admin can lock down for the whole account. Start host-side, because it works immediately and needs no admin.
As the host, during or before a meeting
- Turn on the Waiting Room so nothing joins automatically: Settings > Meeting > Security > Waiting Room. Every join request, human or bot, then waits for you to admit it, and you can simply not admit an unfamiliar "Notetaker".
- Admit participants manually and watch the list. If a bot slips in, hover its name in the Participants panel, click More and choose Remove; removed participants cannot rejoin the same meeting by default.
- Disable the host-side AI: turn off "Meeting summary with AI" (Settings > Zoom AI) if you do not want Zoom itself transcribing.
- Lock the meeting once everyone expected has arrived (Participants > More > Lock Meeting), so no late bot can join at all.
As a Zoom admin, account-wide
The host controls above stop a bot in the room; the admin controls stop it from ever being installable or admissible. In the Admin Center under Settings > General > Security, "Manage which Zoom apps can join as a participant in meetings and webinars in your organization" lets you block specific SDK apps, or allow only the ones you list, so notetaker bots built on the Zoom Meeting SDK can be kept out by name. In the Zoom Marketplace admin portal, under Permissions, "Require published apps to be approved by Marketplace admin" means users can add only the apps you approve (Otter, Fireflies and Read.ai included). Pair that with account-level Waiting Room and "Only authenticated users can join meetings" defaults so anonymous bot accounts are held at the door org-wide.
| Goal | Where in Zoom | Effect |
|---|---|---|
| Hold every joiner for review | Settings > Meeting > Security > Waiting Room | Bots wait for manual admit |
| Remove a bot mid-call | Participants > hover name > More > Remove | Ejected, cannot rejoin |
| Stop late joins | Participants > More > Lock Meeting | No new participant admitted |
| Turn off Zoom AI (formerly AI Companion) | Settings > Zoom AI > "Meeting summary with AI" | Zoom stops auto-summarizing |
| Block bot apps from joining | Admin Center > Settings > General > Security > Manage which Zoom apps can join as a participant | Listed SDK apps blocked, or only listed ones allowed |
| Restrict third-party apps | Marketplace admin > Permissions > Require published apps to be approved | Users add only approved apps |
| Require sign-in to join | Settings > Meeting > Security > Only authenticated users can join meetings | Anonymous bots blocked |
How do I block AI notetakers in Microsoft Teams?
Teams frames this around meeting options and lobby policy. A notetaker bot invited by a guest usually arrives as an anonymous or external participant, so the strongest lever is refusing to auto-admit those categories.
As the organizer, in Meeting options
- Open Meeting options (from the calendar event, or from the meeting controls during the call) and set "Who can bypass the lobby?" to "People in my org". External and anonymous joiners, including many bots, then wait in the lobby instead of walking into the call.
- Leave "People dialing in can bypass the lobby" off (the default) so phone dial-ins wait in the lobby too.
- If a bot is already in, remove it from the participant list. Organizers, co-organizers and presenters can do this; attendees cannot.
- Leave "Record and transcribe automatically" off if you do not want Teams' own recording and transcript starting with the meeting.
As a Teams admin, tenant-wide
In the Teams admin center, under Meetings > Meeting policies, the Meeting join & lobby section has a setting built for exactly this: "Manage external bots and their access to meetings". On its default, "When detected, require approval before joining", Teams marks detected third-party bots and holds them in the lobby until an organizer admits them, even when the lobby setting would let them through. A third option that blocks detected bots outright is rolling out: on 10 November 2026 the Microsoft 365 roadmap (feature 566201) listed it as "Rolling out" and Microsoft’s PowerShell reference already documented it as BlockDetectedBots, while Microsoft’s admin guide to this setting still listed only "Do not detect bots" and the default. Check that your tenant shows it before you rely on it. Microsoft says some bots may not be detected, so keep the other layers: the same section sets the defaults for "Who can bypass the lobby" and "Anonymous users can join a meeting", and Teams apps > Manage apps decides which apps your users may add (on tenants not yet moved to app centric management, this is still Permission policies). Organizers can change lobby defaults in their own Meeting options; to enforce them, Microsoft points to meeting templates or sensitivity labels (Teams Premium).
| Goal | Where in Teams | Effect |
|---|---|---|
| Send external/anonymous to lobby | Meeting options > Who can bypass the lobby? > People in my org | Bots wait in lobby |
| Keep dial-ins in the lobby | Meeting options > People dialing in can bypass the lobby > Off | No straight-through phone joins |
| Hold or block detected bots | Teams admin center > Meetings > Meeting policies > Manage external bots and their access to meetings | Detected bots need approval or are blocked |
| Set lobby default org-wide | Teams admin center > Meetings > Meeting policies > Who can bypass the lobby | Default for every organizer |
| Restrict which apps are allowed | Teams admin center > Teams apps > Manage apps | Block or allow-list bot apps |
| Turn off auto-recording | Meeting options > Record and transcribe automatically > Off | No automatic recording or transcript |
How do I block AI notetakers in Google Meet?
In Google Meet the key setting is the meeting access type, which replaced the old Quick access switch. On Trusted or Restricted access, a bot that is not on the Calendar invite has to ask to join, so an unexpected notetaker never gets in on its own. Add Host management so only hosts and co-hosts can admit, remove and mute people.
As the host, in the meeting
- Open Host controls (bottom right) and set the meeting access type to Trusted or Restricted, not Open. Before the call, the same choice is under Video call options on the Calendar event.
- Turn on Host management in the same panel, so only hosts and co-hosts can admit people, remove them and stop notes.
- When a request comes from an unfamiliar "Notetaker" or a name you do not recognize, click Deny entry. Since March 2026, Meet puts requests that need a closer look in a separate list, where the default action is to deny entry.
- If a bot is already in, click Show everyone (bottom right), then More actions next to its name, and choose Remove from the call. Choosing Block in the box that opens also stops it rejoining this meeting, though not your other meetings.
- If notes start with no bot in the list, that is Google's own Gemini "Take notes for me": click it at the top right and stop it.
As a Google Workspace admin, org-wide
In the Google Admin console you can govern this in two places. Under Apps > Google Workspace > Google Meet > Meet safety settings you set the default Access Type and whether Host management is on by default. Under Security > Access and data control > API controls > Manage App Access you can set the notetaker apps your users connected to Blocked, which cuts the calendar access that drives auto-join. That only covers your own users: a guest from another company can still send their own bot to the meeting link, which is why the access type matters.
| Goal | Where in Google Meet | Effect |
|---|---|---|
| Make bots ask to join | Host controls > access type Trusted or Restricted | Uninvited bots must be admitted |
| Limit who can admit or remove | Host controls > Host management on | Only hosts and co-hosts decide |
| Deny a join request | Join request > Deny entry | Bot never enters |
| Remove a bot mid-call | Show everyone > More actions > Remove from the call | Ejected from the call |
| Restrict third-party apps | Admin console > Security > Access and data control > API controls > Manage App Access | Block/limit OAuth notetakers |
| Set Meet defaults org-wide | Admin console > Apps > Google Workspace > Google Meet > Meet safety settings | Default access type and Host management |
To stop Gemini "Take notes for me" in a call, switch it off for a recurring series or turn it off for the whole organization, follow our step-by-step Google Meet guide.
Why does Otter (or Fireflies) keep joining after I removed it?
This is the most frustrating part, and it is usually not a bug. Most notetaker bots join based on your calendar, not the meeting itself. If someone connected the tool to their calendar and gave it access to a recurring event, the bot re-requests entry for every future occurrence, so removing it once only clears today's instance. A Microsoft Q&A thread shows how this looks from the inside: a user had disabled Otter, and it still kept trying to join their Teams meetings.
How do I disable otter ai note taker from attempting to join my teams meetings?
The durable fix lives at the source: whoever connected the notetaker has to disconnect it from their calendar or turn off auto-join for that meeting series, inside the notetaker's own settings. If that person is unresponsive or unknown, the org-wide admin controls above are the backstop: an app allow-list or lobby default stops the bot regardless of whose calendar invited it. Bitdefender's consumer guidance walks individual users through revoking Otter's calendar access and auto-join for exactly this reason.
Otter AI keeps joining your meetings uninvited? Here's how to make it stop.
IT admins: how do you block AI notetakers org-wide?
Per-meeting toggles do not scale, and they depend on every host remembering to flip them. For an organization, the reliable layer is policy: control the app supply chain and the admission defaults centrally so individual behavior cannot reopen the hole. A practical, platform-agnostic checklist:
- Inventory what is already connected. In each platform's admin center, list the third-party apps and OAuth grants users have authorized, and look for notetaker vendors: this is where the recurring joiners usually originate.
- Switch from block-list to allow-list. Blocking today's named bots is whack-a-mole; permitting only reviewed apps stops tomorrow's too. Zoom (Marketplace pre-approval and the SDK app allow list), Teams (Manage apps), and Google Workspace (API controls) all support this.
- Set an admission default that survives careless hosts. A tenant-wide lobby/waiting-room policy and "authenticated users only" default mean anonymous bot accounts are held even when an organizer forgets.
- Restrict who can grant calendar/OAuth access. Notetakers persist because they hold a calendar grant; limiting which users can authorize third-party apps to your calendar system shrinks the surface.
- Publish a short internal policy. Tell staff which notetaker (if any) is approved and how to disclose recording, so the rules are enforced by norms as well as by console settings. University IT knowledge bases (U. Illinois, UW-Madison) are good models for the tone.
Can attendees block someone else's notetaker bot?
If you are not the host, your options are narrower but real. You can ask the host to remove the bot and enable the lobby/waiting room; you can decline to speak until the recorder is acknowledged; and you can leave. Whether you can remove a bot yourself depends on your role: on Zoom only the host or a co-host can; in Teams, organizers, co-organizers and presenters can; in Google Meet, with Host management off, anyone from the organizer's organization can. An outside guest usually cannot. This is exactly why the durable answer is host and admin configuration, not attendee action.
Is there a way to get notes without policing bots at all?
If you take the notes yourself and you do not want to become the person who polices everyone else's bots, there is a different shape of tool. Reline records on your side: it captures your microphone and the audio coming out of your own computer. Nothing joins the call, nothing appears in the participant list, and there is no bot for anyone to block.
What you get back is the recording and the transcript kept together, so any line plays back from the moment it was said, and notes written a few seconds after you stop. It detects sixty languages on its own, and in the transcript it separates you from the other person. The audio is captured on your computer and transcribed and summarised in the cloud.

It does not stop anyone else's bot. Only the host and admin controls above do that, and you are still responsible for telling people you are recording where the law requires it. What it removes is your own bot from the equation.
Common questions
- Can I block Otter from my Zoom meetings?
- Yes. As the host, enable the Waiting Room (Settings > Meeting > Security) so nothing joins automatically, admit participants manually, and remove any "Otter.ai" that appears in the Participants panel. To stop it account-wide, a Zoom admin can block notetaker apps from joining as participants (Admin Center > Settings > General > Security) and require admin approval for Marketplace apps. The same steps work for Fireflies, Read.ai, and other notetaker bots.
- Why does Otter keep joining after I removed it?
- Because most notetakers join based on someone's calendar, not the individual meeting. If a colleague connected Otter to a recurring event, it re-requests entry for every future occurrence, so removing it once only clears that instance. In a Microsoft Q&A thread, a user who had disabled Otter still saw it trying to join their Teams meetings. The fix is to have whoever connected it disconnect its calendar access or auto-join or, org-wide, block it with an app allow-list.
- Can attendees stop someone else's notetaker bot?
- Usually not. On Zoom only the host or a co-host can remove a participant; in Teams, organizers, co-organizers and presenters can; in Google Meet, people from the organizer's organization can when Host management is off. An outside guest cannot. You can ask the host to remove the bot and enable the lobby or waiting room, decline to continue until the recorder is acknowledged, or leave the meeting. Reliable blocking comes from host and admin settings, not attendee action.
- How do IT admins block AI notetakers org-wide?
- Control the app supply chain and admission defaults centrally. Switch to an app allow-list so only reviewed apps can connect (Zoom Marketplace pre-approval and SDK app allow list, Teams Manage apps, Google Workspace API controls), keep the Teams meeting policy "Manage external bots and their access to meetings" on so detected bots wait for approval, set a tenant-wide lobby/waiting-room and authenticated-users-only default so anonymous bots are held even when a host forgets, and restrict who can grant calendar/OAuth access. Publish a short internal policy so norms reinforce the console settings.
- Is there a notetaker that doesn't join at all?
- Yes. A bot-free notetaker records on your own device instead of sending a participant into the call. Reline captures your microphone and system audio locally, so nothing appears in the participant list and there is no bot for anyone to admit or block, and you still get a transcript and a summary a few seconds after you stop. It does not block other people's bots, and you remain responsible for disclosing recording where the law requires it.
Related posts

Do Zoom, Meet & Teams Notify When You Record or Screenshot?
What Zoom, Google Meet and Teams show others when you record, screen record with OBS, take a screenshot, transcribe or use AI notes, per their own help pages.

AI Notetaker Slack Sharing Controls: Limit What Gets Posted
What Fireflies, Otter, Granola, Fathom and Reline post to Slack after a meeting, who sees it and link previews, and a safe default setup for admins.

What to Tell US Candidates Before Using an AI Notetaker
Before an AI notetaker records a US interview: all-party consent states, Illinois AI and biometric laws, NYC Local Law 144, EEOC duties, and a notice script.
Stop taking notes.Start shipping outcomes.
Free forever for individuals. Five minutes to install. Your next meeting writes its own notes.