How to prevent AI bots from joining Zoom meetings
AI notetakers join Zoom calls as participants, read meeting content through apps, or record quietly on a laptop. Each route needs its own control.
Here are the Zoom web portal settings that keep notetaker bots out, and how to block the services themselves on your network and devices.
Next step
AI Agent Blocklist: block AI notetaker services, their extensions and desktop apps in one file set
Zoom settings guard the meeting. Our list stops staff from reaching, installing and using notetakers you never approved.
From $99 a month for one organisation
Three kinds of AI notetaker in a Zoom meeting
Admins often look for one switch that stops AI bots in Zoom. There is none, because notetakers reach a meeting in three different ways. Knowing which kind you face tells you which control works.
| Joins as a participant | Reads meeting content through an app | Records on the device | |
|---|---|---|---|
| How it gets in | A bot built on Zoom's SDK follows the meeting link, often sent there by someone's connected calendar | An app the account or a user has added receives audio, video or chat from the meeting | A desktop app or browser extension captures sound and screen on a laptop |
| Visible in the meeting | Yes, in the waiting room and participant list | Yes, through the active apps icon | No, nothing appears |
| Zoom control | SDK app allow or block list, authentication, waiting room, recording permission | Zoom Apps settings and Marketplace approval | None inside Zoom |
| Our list | Blocks staff from using the service behind the bot | Blocks the app's service domains | Blocks the app, the extension and the service |
Signs of notetakers in your Zoom account, and who is exposed
Notetakers spread person to person. One sign-up can put a bot into dozens of meetings a week before anyone in IT hears about it.
Signs to look for
- 1Participants named after a tool or "someone's notetaker" that never speak or show video
- 2Hosts get requests to allow recording from participants they do not recognise
- 3The active apps icon shows apps nobody in the meeting added on purpose
- 4Staff receive meeting summaries from services IT never approved
- 5Marketplace requests or installed apps for meeting assistants
- 6DNS or proxy logs show steady traffic to notetaker domains
Who is exposed
Privileged advice and personal cases written down by a third party.
Results, forecasts and deal terms stored outside your systems.
Customer data captured in a tool your customer never agreed to.
Student and patient details covered by strict privacy rules.
If you are still mapping which AI tools people already use, start with an AI agent inventory. It shows how far notetakers have spread before you change settings.
Zoom block AI bots: the web portal settings, in order
Work through these as an account admin. The first setting does the most against participant bots. The rest close the side doors and cut off recording.
Applies to apps built on Zoom's SDK that try to join as participants, which is how most notetaker bots work. Choose an allow list or a block list in the Allow or block Zoom SDK apps dialog.
People and bots must sign in with an approved method before they join. Profiles include Sign in to Zoom, Signed-in users in my account, Sign in to Zoom with specified domains, Signed in to account associated with invited email, and external SSO.
Turn on Allow authentication exception so hosts can let named guests through.
Blocks signed-in users whose email is on a listed domain. Separate domains with commas; wildcards work. It needs authentication profiles, because Zoom can only check the domain of someone who signed in.
Example entries: otter.ai, tldv.io, meetgeek.ai.
Every participant waits until a host admits them. Bots that join as participants show up there with their name. Let users from your own account bypass it so internal meetings stay quick.
Many participant bots ask the host for local recording permission. Untick External meeting participants and leave auto approve off, so outside bots cannot even ask.
Controls apps that receive live meeting content without joining as a participant. Add only approved apps and set participant permissions to Always ask rather than Always allow.
Require admin pre-approval before users add published apps. Approval is set separately for public, unlisted and internal apps. Users can still request an app, which notifies the admins.
Labels participants who are not signed in, or who use an email outside your account, as guests in the waiting room and the participant list. Hosts spot an outside bot at a glance.
Menu names move. Zoom help articles currently use both Admin Center and Account Management, Account Settings for the same area. If a path differs in your portal, search the settings page for the exact setting name.
Settings, plan requirements and app types change often, so check the current admin console before a company-wide change.
Lock the settings so hosts cannot switch them back
Zoom settings exist at account, group and user level. A setting you turn on but do not lock is only a default, and any host can undo it before the next meeting.
Turn the setting on and lock it for every user. Use this for the SDK app list, Marketplace approval and recording requests from external participants.
Put HR, legal, finance and leadership in their own group with strict authentication and a domain block. Lock it at group level. Groups live under Users, Groups.
Users change only what is not locked above them. A greyed-out setting means a group or account admin has locked it, which is what you want.
Watch the trade-off. Strict sign-in rules can stop customers and candidates without Zoom accounts. Apply them to sensitive groups first, and give hosts the authentication exception for named guests.
When a notetaker is already in the meeting
Settings stop the next bot. For the one sitting in today's call, the host has four quick moves.
Remove it
Open Participants, hover over the bot, open the more menu and choose Remove.
Lock the meeting
Under Security, choose Lock Meeting so no new participants, bots included, can join.
Stop content sharing to apps
In Host tools, turn off Share realtime meeting content with apps if an app is receiving content.
Check active apps
The active apps icon at the top of the meeting window lists apps reading content, what they access and who runs them.
Afterwards, find out whose calendar sent the bot. Notetakers usually join because one attendee connected their calendar, so the lasting fix is a conversation with that user and a block on the service.
What Zoom settings cannot reach
Even a fully locked Zoom account leaves four gaps. These are the reasons meeting data can still reach outside services after the settings are done.
Recorders on the device
Desktop notetakers and browser extensions record audio from the laptop. They never join, so no Zoom setting sees them.
Meetings hosted elsewhere
When your staff attend a customer's Zoom meeting, that customer's settings apply. Your staff's own notetaker can follow them in.
Calendar connections
The bot gets its meeting links from a work calendar that a user connected. Zoom cannot remove that connection; your email platform's consent settings can.
Uploads after the meeting
People upload recordings to a notetaker's website to get a transcript. That is a web upload, outside Zoom entirely.
All four end at the same place: the notetaker's own service. Blocking that service on your network and devices closes them together. The same approach works for AI bots in Teams meetings.
Block notetaker services with the AI Agent Blocklist
Our list includes AI meeting and voice agents as one of its agent categories: the notetaker services, their browser extensions and their desktop apps. Load it where your rules already live.
| Where you load it | File from the download | What it stops |
|---|---|---|
| DNS filter | DNS filter import file or plain domain list | Sign-ups, web apps and uploads to notetaker services from any device on your DNS. See DNS blocking. |
| Firewall or web gateway | Firewall external list format | The same services at the network edge, refreshed from a URL. See firewall blocking. |
| Chrome and Edge policy | Extension block lists | Meeting recorder extensions. Steps in block AI browser extensions. |
| Intune or Jamf | Windows and macOS identifiers | Desktop notetaker apps on managed laptops. Mac steps in Jamf. |
meimoidfecamngeoanhnpdjjdcefoldnio.tldv.desktopGranola.Granolafireflies.aiA few examples only. Every entry in the files carries the tool name, category, identifier type and a risk grade.
Every notetaker service, extension and desktop app you have not approved. Start with the higher-risk grades if you want a gentler first step.
New entries in the meeting agent category and repeat attempts to reach blocked services. Repeat attempts usually mean someone needs a sanctioned option.
The one meeting assistant your organisation approved, whether a third-party service or Zoom's own, placed above the block rule and in your SDK app allow list.
Four decisions to make before you change settings
Settings follow policy. If nobody has decided what is allowed, every blocked bot turns into an argument. Settle these four questions with legal, HR and the business owners first.
Do we allow any AI notetaker?
Most organisations pick one approved assistant, or none, and block the rest. An approved tool gives people a sanctioned option, which cuts the pressure to sign up for something on their own.
Who may record, and when?
Decide whether recording needs the host's consent, every participant's consent, or is banned for certain groups. Your recording permission settings should match that answer exactly.
What about a guest's bot in our meeting?
A customer may bring their own notetaker. Write down whether hosts should admit it, ask first, or remove it, so hosts are not left to judge on the spot.
What about our bots in their meetings?
Staff who join a customer's meeting with an unapproved notetaker put your company's name on that recording. The block on the service is what stops this, since the customer's Zoom settings apply there, not yours.
Put the answers into your acceptable use rules and tell people why. Hosts follow a rule they understand far more readily than a setting that suddenly blocks a tool they liked.
Rollout checklist
This order avoids a week of help desk tickets. Our AI agent risk assessment helps you decide which meetings deserve the strict group.
- List the notetakers already in use from Marketplace, logs and staff
- Decide on one approved assistant, or none, and write it down
- Turn on the SDK app setting with an allow list for the approved app
- Turn on Marketplace pre-approval for published apps
- Stop external participants from requesting local recording
- Create a strict group with authentication and a domain block
- Lock every setting at account or group level
- Load the notetaker category into DNS, firewall and browser policy
- Brief hosts on removing bots and locking meetings
- Review blocked traffic and app requests every week
The AI Agent Blocklist
One list for notetakers and every other AI agent
Meeting agents are one category among AI browsers, autonomous agents, agent extensions, coding agents and MCP servers. You choose which categories and risk grades to block. Read more about the AI Agent Blocklist or the wider guide to blocking AI agents.
Updated every day. After an order we set up your download access within one business day.
Ask us or order a plan
Tell us what you need to block and where your rules live. We reply within one business day.
- Files for firewalls, DNS filters, secure web gateways, MDM and browser policies
- Updated every day as new AI browsers, agents and extensions appear
- Plans for one organisation, for MSPs and for product makers, or a hosted filter we run for you
Zoom AI bot questions
Can Zoom block AI bots automatically?
There is no single switch that stops every notetaker. Admins can allow or block the SDK apps that join meetings as participants, require sign-in, block domains, limit who can ask to record and require approval for Marketplace apps.
Desktop notetakers that never join the meeting need device and network blocking.
How do I prevent AI bots from joining Zoom meetings?
In the Admin Center go to Settings, General, Security and turn on Manage which Zoom apps can join as a participant in meetings and webinars in your organization, then allow only the apps you approve.
Add authentication, a waiting room and a domain block, and stop external participants from requesting local recording.
Does blocking a domain in Zoom stop Otter or Read AI?
Only in part. The domain block checks the email domain of signed-in users, so it needs authentication profiles and it only catches a bot that signs in with an account on that domain. Bots that join another way need the SDK app list and the waiting room.
Can an AI bot record a Zoom meeting without the host's permission?
Participant bots that record through Zoom's local recording need the host to grant permission. If external participants cannot request recording permission, that route is closed. A desktop app recording audio on someone's own computer does not ask Zoom at all.
How do I remove an AI notetaker that already joined my Zoom meeting?
Open Participants, hover over the bot, open the more menu and choose Remove. Then use Security and Lock Meeting so it cannot come back, and check whose calendar invited it.
Will requiring sign-in break meetings with customers?
It can, if customers do not have Zoom accounts. Use authentication profiles that match each group, apply strict settings to sensitive groups first and let hosts add authentication exceptions for named guests.
How often does the notetaker block list change?
The AI Agent Blocklist is updated every day. New meeting assistants, their extensions and their desktop apps are added as they appear, so your firewall, DNS filter and browser policies pick them up without manual edits.
Zoom is a trademark of Zoom Communications, Inc. Microsoft Teams and Intune are trademarks of the Microsoft group of companies.
Chrome is a trademark of Google LLC. Jamf is a trademark of Jamf Software, LLC.
Otter.ai, Read AI, Fireflies.ai, tl;dv, MeetGeek and Granola are trademarks of their respective owners. Names are used only to identify the products discussed. AI Agent Blocklist is not affiliated with, sponsored or endorsed by these companies.