Before choosing an AI meeting assistant, ask whether it can join your meetings and what access it needs. Microsoft's Teams meeting policy defaults to RequireApprovalWhenDetected for detected external bots. Google Meet hosts can restrict access for uninvited participants, and Zoom's Marketplace app pre-approval defaults differ by account type. These are distinct controls, not one universal rule for every assistant.
An AI meeting assistant may join a meeting as a bot to transcribe or summarise it, or it may capture audio while you attend. Bot-based tools need to clear the meeting's join controls; browser-based tools face capture permissions instead.
Feature lists alone cannot tell you whether a tool will work in your organization. Ask who admits it and what data it can access. This guide covers those questions; our AI note taker comparison covers features and prices.
Key takeaways
- Microsoft Teams ships the
ExternalBotAccessModemeeting policy withRequireApprovalWhenDetectedas the documented default: a detected bot waits in the lobby until an organizer admits it. - Microsoft also documents the failure mode nobody quotes: detection can misclassify a human as a bot, and the fix is admitting them and marking "This is not a bot."
- Zoom's Marketplace app pre-approval has different documented defaults for single-user and multi-user accounts that have not yet accessed Marketplace. Check your account's current setting.
- Admission and authorisation are two different gates. Being let into the room says nothing about what the assistant may then read from your calendar, your storage or your CRM.
- A browser capture tool does not need meeting admission, but it still needs your browser permission and may be restricted by organization policy. It cannot auto-join meetings you do not attend.
Why admission matters when picking an AI meeting assistant
For years the buying question was quality. Which AI meeting assistant writes the better summary, catches the action items, handles the accent. That question still matters. It just stopped being the first one.
Microsoft explains why Teams checks external bots: they may "record or transcribe meetings without participant awareness" and "store meeting data in third-party systems outside of the organization's compliance boundaries." Other platforms use different controls, so check the rules for the account that hosts your meetings.
That warning does not mean every assistant is blocked. It means a successful personal trial may not predict what happens in a managed account.
Microsoft Teams: approval is the default, not the exception
Teams detects external bots during the join process and applies an admin policy to what it finds. Microsoft's admin documentation lists these two values for the ExternalBotAccessMode attribute:
AllowBots: "Bots aren't detected or marked in the lobby or in the meeting. They appear as any other external participant."RequireApprovalWhenDetected: the documented default. Detected bots are marked and held until an organizer explicitly admits them.
Microsoft advises admins to restrict lobby admission to organizers and co-organizers. That is a recommended configuration, not a guarantee on every Teams tenant. Detection is also imperfect in both directions.
Microsoft documents that "some external bots may not be detected," and separately that "detection may occasionally misclassify human participants as bots." The remedy for the second case is admitting the person from the lobby and marking them with the "This is not a bot" option. A genuine colleague can get stuck behind a control aimed at your note-taker.
If you are evaluating an AI meeting assistant for a Teams-heavy organisation, that's the question to ask the vendor: what does your product do when it's held in the lobby and nobody admits it? Does it retry, fail silently, or send the organiser an email?
Google Meet entry and Zoom app approval work differently
Google Workspace guidance says Meet hosts can set access to Restricted, so an uninvited app participant must ask to join. Admins can make that the default for meetings they host. Google also describes controls for app domains, extensions and API access. Check the host's meeting setting and the app's requested access separately.
Google's guidance does not establish a universal risk score or a blanket default denial for all third-party assistants. If you are testing one, ask the meeting host which access setting applies and whether the administrator has blocked its domain, extension or API access.
Zoom's Marketplace admin documentation says pre-approval is disabled by default on single-user accounts that have not yet accessed Marketplace, and enabled by default on multi-user accounts that have not yet accessed it. Admins can change the setting and approve individual apps. This is an app-installation control; it does not by itself describe whether a meeting host will admit a bot.
A trial on a personal Zoom account may therefore miss the approval step a team account uses. Ask the admin to check the current Marketplace setting before assuming either outcome.
What data your AI meeting assistant can access
Meeting admission and data authorization are separate decisions. An app may ask for account access before it joins a call, and the meeting host may still deny it entry.
Depending on the product and configuration, an assistant may request calendar access to schedule joins, workspace access to read meeting data, or CRM write access for follow-ups. Check the actual consent screen and vendor retention policy before granting access.
Scope matters: read access and write access do different things, and the exact data visible to a vendor depends on the permission granted. Ask whether a calendar connection can be limited, where transcripts are stored and when they are deleted.
For Google integrations, apps requesting sensitive or restricted OAuth scopes generally need verification unless an exception applies. A restricted-scope app that handles the data on a third-party server may also need a security assessment. Ask the vendor which scopes its specific integration requests.
For the data-handling side of the decision, see our separate guide to recordings, summaries and privacy.
Three platforms, different approval points
| Platform | What happens when an assistant asks in | Who decides |
|---|---|---|
| Microsoft Teams | Detected bots are marked and held for explicit admission under the default RequireApprovalWhenDetected policy value, per Microsoft's admin docs. |
Admin sets the policy; organizer admits in the moment. |
| Google Meet | Uninvited app participants must ask to join when the host sets access to Restricted, per Google's guidance. | Host controls meeting entry; admin can set defaults and restrict apps or API access. |
| Zoom | Marketplace app-installation pre-approval defaults differ on new single-user and multi-user accounts, per Zoom's admin docs. | Account owner or admin sets approval; the meeting host controls meeting admission separately. |
| Browser-tab capture | The capture tool does not join, so the lobby does not apply to it. Chrome capture policy can restrict sharing. | The user chooses a tab; organization policy may restrict capture. |
Two illustrative workflows
Both scenarios below are illustrative examples written to show how the two gates interact. They are not customer stories, and the people in them are invented.
Illustrative: the assistant that never made it into the call
Priya runs partner calls on Teams for a logistics firm. She connects an assistant to her calendar, but a detected bot waits in the lobby under the default Teams policy. Nobody admits it, so the meeting ends without a transcript from that tool. Her team needs an owner for lobby admission or a different capture approach before it can evaluate summary quality.
Illustrative: the trial that worked, then stopped working
Marco tests a Marketplace app on a single-user Zoom account where pre-approval is disabled. His operations team then tries it on a multi-user account where an admin has kept approval enabled. They must review the app before installation. The difference comes from account settings, not a change in the product.
Where MirrorCaption sits, and what it deliberately cannot do
It's worth being direct about this, because the argument above cuts both ways.
MirrorCaption is not an agentic AI meeting assistant. It doesn't auto-join from your calendar, write to your CRM or attend a meeting while you're elsewhere. If those capabilities matter, compare a bot-based product; our Otter.ai comparison explains a different trade-off.
On desktop Chrome or Edge, you can share a meeting tab for live transcription and translation while you attend, then use MirrorCaption's summary features. It does not add a participant to that meeting. Browser permission is still required, and your organization can restrict capture or access to the service. A microphone can be used when tab capture is unavailable.
Chrome Enterprise's ScreenCaptureAllowed policy can disable screen-sharing APIs, while related origin policies can grant exceptions. Check your organization's effective browser policy rather than assuming capture works. For capture mechanics, see our guide to meeting notes without a bot.
How to choose an AI meeting assistant your organisation will actually admit
Five questions, in the order that saves you time:
- Which platform hosts most of your meetings, and who is your admin? The answer tells you which controls to check before a trial.
- Does the tool join as a participant? If yes, check meeting admission. If it captures locally, check browser permission and device policy.
- What scopes does it request, and can you say no to some of them? A product that degrades gracefully without CRM write access is easier to approve than one that demands everything up front.
- Where does content live, and for how long? Ask before the trial, because the answer is what your admin will ask you.
- What happens in the failure case? Held in the lobby, denied by an admin, blocked by device policy. A vendor who answers this crisply has seen it before.
Run those five before comparing summary quality. A tool that cannot access the meeting in your real environment cannot deliver its promised workflow.
The bottom line
Teams holds detected bots under its documented default policy; Meet hosts can require uninvited participants to ask to join; and Zoom Marketplace app approval depends on account settings. Those controls operate at different points. Check the meeting, installation and data-permission steps independently.
Pick the tool whose capabilities match what you need, then check its meeting, installation, data and capture permissions in your environment. If you need live captions and translation while attending a browser meeting, tab capture is one option to test.
Read every word, in your language, while the meeting runs
Try live captions and translation while you attend. Desktop tab capture does not add a bot to the meeting; check current trial terms and plan prices in the app.
Get Started FreeFrequently asked questions
Will my AI meeting assistant be blocked from joining Teams meetings?
Not blocked outright, but held. Microsoft's default meeting policy value is RequireApprovalWhenDetected, which places a detected bot in the lobby until an organizer explicitly admits it. An admin can switch the policy to AllowBots, and Microsoft notes some bots may not be detected at all.
Do I need admin approval to use an AI meeting assistant?
It depends on the platform, account settings and requested permissions. Teams organizers admit detected bots under the default policy; Google Meet hosts can restrict uninvited participants; Zoom administrators can require app approval. Browser capture needs your permission and can be limited by device policy.
What permissions does an AI meeting assistant ask for?
Check the specific product's consent screen. Some tools request calendar access to auto-join, while others request workspace or CRM access. Google requires verification for sensitive or restricted OAuth scopes unless an exception applies. Ask where transcripts are stored and for how long.
Can I use an AI meeting assistant without it joining the meeting?
Yes. With browser-tab capture, the tool does not join as a participant, so the meeting lobby does not apply to that tool. The browser still asks you to choose what to share, and an organization can restrict capture. It cannot auto-join a meeting you do not attend.
Is MirrorCaption an AI meeting assistant?
Only in the narrow sense. MirrorCaption offers live transcription, translation and summaries while you attend. It does not auto-join from your calendar or write back to a CRM. Desktop browser-tab capture requires a browser permission and may be restricted by organization policy.