Keep meeting recordings and transcripts need-to-know
Recordings and transcripts are sensitive by default — comp talk, deal terms, health details. Gate who an agent can pull them for, and mask what it returns.
For: Teams letting an agent summarize or search Zoom meetings
Meeting recordings and transcripts are among the most sensitive content an agent can read, precisely because they capture things people say out loud that they'd never put in a document: compensation, deal terms, personnel decisions, sometimes health details. A "recap this call" request reads the whole transcript wholesale.
The policies keep that content on a need-to-know footing. guard-transcripts-by-group gates retrieval of recordings and transcripts to an authorized group, so not every agent user can pull every meeting. redact-pii-meeting-intelligence masks personal data in the transcript and summary output. fence-agentic-search constrains the meeting-search surface, and block-secrets-chat catches credentials pasted into meeting chat before they land in a summary.
Use group-gated retrieval where recordings carry regulated content, and layer egress redaction on top for the reads you do allow.
Policies in this guide
Gate Zoom Transcripts & Recordings by Group
Gates retrieval of Zoom meeting transcripts, AI Companion summaries, and next-steps on the connector's core egress tools, enforcing minimum-necessary access:
Zoom: Redact PII in Meeting Intelligence
Scans the responses of Zoom's meeting-intelligence read surfaces — AI summaries, verbatim transcripts, recording resources, and Zoom Docs content — and…
Fence Zoom Agentic Search to Native Corpora
Constrains Zoom's agentic-search tool ( search zoom) so it can only reach Zoom-native content.
Block Secrets in Zoom Team Chat
Blocks Zoom Team Chat send/update tool calls whose message content looks like it contains a live secret — API keys, passwords, bearer tokens, or…