Set up Google Meet compliance recording

Exporting your Workspace data using local data storage is available only for users with the Assured Controls or Assured Controls Plus add-on. Additional charges for Google Cloud Storage may apply. Contact Google Cloud Support for any billing or usage questions.

You can turn on compliance recording for archiving that automatically records meetings and captures transcripts in Google Meet for specific users or groups. This helps you to meet regulatory requirements—for example, those from the Financial Industry Regulatory Authority (FINRA).

When you turn on compliance recording for a user, their Meet meetings are recorded and the transcripts are captured. Both are stored in WORM (write once, read many) compliant Google Cloud Storage (GCS) with appropriate retention policies.

Compliance recording restrictions

The following restrictions apply to compliance recordings:

• Users can't access compliance recordings. If a user needs to record or transcribe a meeting, they must do it themselves during the meeting.
• There's a maximum recording duration of 8 hours. If a meeting exceeds this limit, monitored users might be removed from the meeting.
• Compliance recordings include a metadata file containing information like Meeting ID, start and end times, attendee names, and file type.
• Compliance recordings aren't automatically shared with attendees or linked to Google Calendar events. Users also don't receive email notifications for these recordings.
• Phone dial-in and anonymous participants aren't monitored independently. However, they are monitored if another non-anonymous, monitored meeting participant is present.
• Captions aren't the official text record. Transcripts are the source of truth for text records.
• Meet doesn't monitor meetings based on the Calendar invite list. Compliance recording always begins when a monitored user joins a meeting.
• When monitored users join breakout rooms, the recording won't capture the breakout room.

Before you begin

To ensure WORM compliance, make sure your GCS bucket has appropriate retention policies configured using Bucket Lock. Your bucket must be shared with the service account listed under Destination. You must also grant the service account the following permissions:

• Storage Legacy Bucket Reader
• Storage Object Viewer
• Storage Object Creator

For details, go to Bucket Lock.

Control who uses Meet compliance recording in your organization

1. Sign in with an administrator account to the Google Admin console.

   If you aren’t using an administrator account, you can’t access the Admin console.

2. Go to Menu  Apps > Google Workspace > Google Meet.

   Requires having the Service Settings administrator privilege.

3. Click Compliance.
4. (Optional) To apply the setting only to some users, at the side, select an organizational unit (often used for departments) or configuration group (advanced). Show me how

   Group settings override organizational units. Learn more

5. Check or uncheck the Compliance archive recordings box.
6. For Recording options, select one of the following:
   • Audio
   • Audio & video
7. For Destination, in the Google Cloud bucket field, enter your GCS bucket's  name.
8. Click Save.

How compliance recording works

Before a meeting

If a monitored user is in the meeting, a Meet is producing its own secured recording for compliance message is shown on the pre-meeting screen.

During a meeting

• The Compliance badge (shown above) is shown to all meeting participants if a monitored user is present or listed on the Calendar invitation.
• The Compliance badge can't be turned off.
• Clicking the Compliance badge shows details like Meet is recording for compliance and About this recording.
• If a regular recording is in progress, two distinct badges are shown. 
• If compliance recording doesn't start, or there's an issue mid-meeting, monitored users might be removed from the meeting. This typically happens when the GCS storage bucket is missing correct permissions, or the recording or transcription fails. If a monitored user is removed from a meeting, a You exited the call because Meet couldn't perform required recording message is shown.
• If a monitored user joins a meeting in progress, compliance recording starts at that point.