Ir al contenido
Comma Compliance Docs

Setting Up Google Workspace Archiving

Esta página aún no está disponible en tu idioma.

Connect a Google Workspace domain, select the surfaces you need, and have a Google super-admin authorize domain-wide delegation. Each connected workspace has its own permissions and coverage view.

How Google Workspace capture works

Section titled “How Google Workspace capture works”
  • Gmail - mailbox messages and attachments for the configured capture scope.
  • Drive - accessible files from eligible users’ Drives and Shared Drives, metadata and deletion markers. Each sync captures the visible file version. Pre-connection revision history and intermediate edits between syncs are not captured. Google-native Docs, Sheets and Slides are archived through Google’s export API, which sets the size and format limits below. File comments and a complete user-activity log are outside this scope.
  • Chat - direct messages and spaces, including Chat-uploaded attachments. Shared Drive files remain references unless the required Drive access is separately enabled.
  • Meet - available meeting artifacts, including recordings and transcripts where the Google edition and source configuration provide them.
  • Calendar - authorization can be configured, but Calendar event archival ingestion is not included in this capture scope.

Drive file and format limits

Section titled “Drive file and format limits”

Google sets these boundaries, not Comma. Google-native files are converted on the way out of Drive, and Google’s export API decides what it will hand over.

  • Docs, Sheets and Slides export up to 10 MB each. Google’s export API refuses anything larger, so a native document above that ceiling is not archived.
  • Drawings, Forms, Jamboard, Apps Script and My Maps are not archived. Google provides no way for an archiving tool to retrieve them.
  • Uploaded files - PDFs, Office documents, video, images and anything else stored in its original format - are archived up to 5 GB each. They are copied as-is, so no export conversion applies.

If your firm keeps records in Google-native formats, check the size of the documents that matter before you rely on Drive capture for them.

The workaround. Where a document is over the 10 MB ceiling, or is one of the file types Google will not export, download it as a PDF or a Word, Excel or PowerPoint file and upload that copy to Drive. Comma archives uploaded files as they are, up to 5 GB each, so neither the ceiling nor the export step applies.

Authorize the surfaces you need

Section titled “Authorize the surfaces you need”

Each surface is an independent toggle. The authorization card shows the exact read-only scopes for your selection, plus the Directory scope needed to identify workspace users.

Gmail starts enabled on a new workspace. Other surfaces are added explicitly. Selecting a new surface may require an updated delegation grant and verification.

Prerequisites

Section titled “Prerequisites”
  • Google Workspace Super Admin
  • Comma team admin access
  • A Google edition and source settings that produce the artifacts you need, particularly Meet recordings.

Setup steps

Section titled “Setup steps”
  1. Sign in to the Comma Compliance dashboard
  2. Open Integrations in the top navigation
  3. Under Workspace Integrations, find the Google Workspace card and click Connect
  4. Sign in with a Google Workspace account on the domain you want to connect.
  5. Confirm the primary domain and choose the surfaces to archive.
  6. Open the domain-wide delegation grant card. Copy the Client ID and exact scope strings shown by Comma.
  7. Have a Google super-admin open Security > Access and data control > API controls > Manage Domain-Wide Delegation in the Google Admin console.
  8. Add the Client ID and selected scopes, then authorize the grant.
  9. Return to Comma and choose Verify access. Review the result for each enabled surface.

If another administrator owns Google access, use Send to admin for the grant instructions, a standalone link or a printable page. Delegation changes may take up to 24 hours to propagate.

Verifying capture

Section titled “Verifying capture”

Authorization and capture are separate checks. A verified grant is shown as Access verified, not synced yet until an archival cycle supplies the required coverage signal.

  • Confirm the connected domain and enabled surfaces.
  • Resolve missing scopes or authorization failures shown in the coverage panel.
  • Review actual sync and coverage results for the configured users.
  • Use representative source content to verify the artifacts your deployment needs.

Removing the integration

Section titled “Removing the integration”
  1. From the Google Workspace card in Comma, click Disconnect
  2. Have your Google super-admin review and remove the associated domain-wide delegation grant if it is no longer needed.
  3. Historical capture remains under your retention policy

What’s next

Section titled “What’s next”