Metric 0.1
3 platforms
Participant-level controls
Teams, Meet, and Webex document controls that can screen, deny, or block external bots.
Public tracker · Updated August 2026
The Meeting Bot Ban Tracker
A sourced record of platform restrictions, institutional policies, lawsuit filings, and attributed public reports concerning third-party meeting bots.
Metric 0.2
15 institutions
Tenant restrictions
Universities and public institutions with a sourced restriction or documented block.
Metric 0.3
24/24 sourced
Public-source coverage
Every active record links to a specific policy, advisory, docket, opinion, or notice.
Metric 0.4
6 legal records
Litigation & guidance
Filings and opinions are labeled by procedural status without implying liability.
Evidence timeline
2026ACTIVE PHASE
2025EXPANSION PHASE
2024GENESIS
2023EARLY SIGNAL
The architecture split
Bot bans can block a participant.Local capture has no participant to block.
Platform controls can quarantine a third-party account. Local capture creates no guest account to admit, flag, or remove.
Blocked by participant-level bot controlsQuarantined
Guest account joins
A vendor-controlled participant enters the meeting roster.
Lobby policy evaluates it
Tenant controls can flag, hold, or deny the untrusted participant.
Meeting access depends on approval
The workflow breaks when the organizer or administrator refuses entry.
Not affected by participant-level bot bansNo bot to block
No external participant is created
There is no bot, guest identity, calendar attendee, or external roster entry for the meeting platform to inspect.
Windows captures local playback
Audio is read from the device's own system-audio path rather than from a meeting account.
Participant-level bans have no target
Because no bot joins, controls designed to quarantine or reject bot participants do not apply to this capture path.
Scope note: this comparison is only about participant-level bot bans. Local capture still remains subject to consent, disclosure, device-security, retention, organizational policy, and applicable law.
Documentation & analysis
Technical & legal background
Why are organizations restricting meeting bots?
Published reasons include participant-level security controls, confidentiality and data-egress concerns, privacy claims, and organizational consent requirements. Read each record with its linked source.
Is every restriction a universal ban?
No. Controls vary by platform, tenant, institution, meeting type, and administrator. The tracker separates policies, institutional restrictions, filings, commentary, and data points.
Does local capture remove consent requirements?
No. A bot-free architecture changes whether an external participant joins. It does not replace organizational recording policy, disclosure obligations, or applicable law.