Skip to content

Compliance

Planned Roles: Workspace admin, Owner, Security reviewer Platforms: Web, Mac, Windows, Linux Reviewed: 2026-03-14

Compliance

Section titled “Compliance”

Use this page when a security, procurement, or legal reviewer needs more than feature-level docs. It is written as planning guidance for regulated or policy-heavy deployments, not as a substitute for formal attestation material or contract language.

Current documentation posture

Section titled “Current documentation posture”
  • This page is marked Planned because formal compliance guidance can differ by deployment, contract, and evidence process.
  • Use the security, permissions, and data-protection docs to understand the product boundary first.
  • Use formal review channels when a customer or regulator needs attestations, reports, residency commitments, or contractual terms.

Before starting a compliance review

Section titled “Before starting a compliance review”
  • Define which frameworks or internal policies are actually in scope.
  • Document the workflow boundary: where data is created, who can access it, how long it is retained, and where it can be exported.
  • Review identity, permissions, integrations, and deletion behavior together instead of answering each in isolation.

Topics a reviewer will usually ask about

Section titled “Topics a reviewer will usually ask about”
  • Meeting access and guest controls
  • Artifact visibility for summaries, transcripts, recordings, and exports
  • Retention and deletion behavior
  • Identity and admin controls
  • Downstream sharing into Slack, Notion, exports, or other systems

What this page should not imply

Section titled “What this page should not imply”
  • Do not treat preview docs as a full list of certified controls.
  • Do not answer regulatory or contractual questions with UI screenshots alone.
  • Do not assume the same review package applies to every deployment environment.

Troubleshooting

Section titled “Troubleshooting”

A reviewer wants a single short answer for a complex workflow

Section titled “A reviewer wants a single short answer for a complex workflow”
  • Answer with the workflow boundary first: creation, access, retention, and export.
  • Link to the specific docs pages that describe those controls in product terms.
  • Escalate to formal evidence channels when the question moves beyond product behavior and into attestations or contractual obligations.
Section titled “Related tasks”