# Meeting Recording and Transcript Archiving

Archive available Zoom, Teams and Google Meet recordings and transcripts. Review source coverage, permissions and recording requirements.

Source: https://commacompliance.com/meeting-recording-archiving

---

Meetings & Voice

# The meeting ends. The record still matters.

Preserve available meeting recordings and transcripts with the business conversation they document.

[Review meeting coverage](/get-in-touch)

## More than a calendar entry

The recording, transcript and participant context can tell different parts of the same story. Comma’s native meeting connectors retrieve available artifacts from Zoom, Microsoft Teams and Google Meet. Capture depends on the source platform producing those artifacts and granting access to them.

Available artifacts depend on source permissions and recording settings.

## Know what each source can provide

| Source | Capture scope | Deployment requirements |
| --- | --- | --- |
| Zoom | Available cloud recording video, audio and transcripts, associated with a meeting record. | Enable the meeting surface and grant recording access. Local recordings are outside this cloud capture path. |
| Microsoft Teams | Available recordings and transcripts for meetings organized by monitored users. | Enable the recording surface, grant permissions and authorize applicable metered content downloads. |
| Google Meet | Available meeting artifacts for eligible connected workspace users. | Workspace delegation, enabled capture and a Google edition that produces the required artifacts. |

## Connection is only the starting point

An authorized connection does not prove a recording was captured. Zoom’s coverage view separates permissions, licenses, capture activity and known gaps. A source recording deleted before retrieval, or a missing transcript, needs to be visible when assessing coverage.

For Teams, a meeting’s metadata can be present while a content download still requires authorization. For Meet, the edition and source settings determine which artifacts exist. We review these conditions with your administrators before rollout.

## Already using a meeting notetaker?

Native meeting capture and a notetaker integration are separate connections. If your team uses Fathom, Fireflies, Otter or another recorder, tell us which workspace and artifacts you need. We’ll confirm connector availability and scope rather than assume the native meeting connection includes that service’s summaries or action items.

## See the record, then evaluate the workflow

Ask for a walkthrough using your intended platform: the source meeting, its available recording and transcript, the archived record and its coverage status. Include your administrator so permissions and source requirements are part of the same conversation.

Read the [Zoom setup guide](https://docs.commacompliance.com/getting-started/zoom-setup/), browse [platform integrations](/platform-integrations), or explore [CRM conversation sync](/crm-records-and-sync).

## Bring your meeting workflow to the demo.

We'll show the capture path, source requirements and coverage controls for your environment.

[Book a walkthrough](/get-in-touch)[Pricing](/pricing)