Required Zoom Admin Settings

Comma captures Zoom data through admin-scoped Zoom APIs. For capture to work, certain settings must be enabled in your Zoom admin console. Missing settings cause silent gaps - meetings archive but chat is missing, or phone calls appear without transcripts.

Work through each section below first, then follow Setting Up Zoom Archiving to create the connection.

Recording settings

Go to Zoom Admin > Account Settings > Recording.

Setting	Required value	Why
Cloud recording	On	Comma ingests recordings from Zoom cloud storage; local recordings are not accessible via API
Audio transcript	On	Enables searchable text alongside call and meeting audio
Save chat messages from the meeting	On	Archives in-meeting chat; off by default on many accounts
Save closed captions	On	Supplementary transcript for accessibility and search
Recording disclaimer	Optional	Not required for capture, but recommended per your policy

To enable for specific users only (rather than all users), go to User Management > Groups, create a group for the users in scope, and apply the recording settings at the group level.

In-meeting settings

Go to Zoom Admin > Account Settings > Meeting.

Setting	Required value
Chat	On
Auto save chats	On
Private chat	On or Off, per your policy — either way, Comma captures what’s enabled
Meeting reactions	On if you want reactions in the archive

Zoom Phone settings

Go to Zoom Admin > Phone System Management > Settings.

Setting	Required value
Call recording	On (Automatic or On-demand, per your policy)
SMS/MMS	On if users send texts via Zoom Phone
Voicemail transcription	On
Recording storage	Cloud (not local)

Comma only captures calls where cloud recording is active. Check that users in scope are assigned a Zoom Phone license and have recording enabled at the user level if your policy uses user-level overrides.

Connecting Comma to Zoom

Comma connects using a Server-to-Server (S2S) OAuth app that your Zoom admin creates in the Zoom Marketplace, then grants admin scopes for each surface you want to capture. The full click-path - creating the app, adding the granular admin scopes, configuring the webhook Event Subscription, and pasting the credentials into Comma - is covered step by step in Setting Up Zoom Archiving.

A one-click Marketplace install is coming soon (pending Zoom’s security review). Until then, the Server-to-Server setup is the supported path.

If a surface reports a missing scope after connecting, add that scope to your Server-to-Server app and Comma picks it up on the next check - see the honesty badges under “Verifying everything is working” below.

What isn’t captured yet

The Zoom connector currently covers Team Chat, Zoom Phone (calls, recordings, voicemail), SMS/MMS, and meetings (cloud recordings and transcripts). Zoom Webinars are not captured yet. Enabling webinar recording and chat settings now does no harm and readies your account, but webinar content will not appear in the archive until webinar capture ships.

Verifying everything is working

After enabling these settings and connecting Zoom, run a test:

Host a 2-minute Zoom meeting with cloud recording on
End the meeting
Wait 5 to 10 minutes for Zoom to finalize the recording and push it to Comma
In Comma, open Messages and filter to Zoom - the meeting recording and transcript should appear

If content is missing, open the Zoom section of Comma’s Configuration Center and check the per-surface honesty badges. Each enabled surface reports its own status - Connected, Connected but not yet archiving, Missing scope, No Zoom license, or Authentication failed - so a gap tells you exactly which scope or license to fix rather than failing silently.

Next steps

Setting Up Zoom Archiving — connect the integration from the Comma side
Inbound Webhooks — push other voice or meeting data into Comma