Skip to main content

Integration · Email + collaboration

On roadmap — not yet shipped

ClarityLift + Google Workspace

Google Workspace integration for Google Chat spaces. Roadmap — not yet shipped. Out of scope for V1: Gmail content.

Signals derived from Google Workspace

Team friction (Google Chat spaces)

Communication health

Silence

OAuth scopes ClarityLift requests

Every scope below has a documented purpose tied to a specific step in the data flow. ClarityLift never requests scopes it does not use.

chat.spaces.readonly

List Google Chat spaces

chat.messages.readonly

Read messages in connected spaces

admin.directory.user.readonly

Resolve directory users for the consent gate

Data flow, end to end

  1. 1Workspace admin installs the ClarityLift Marketplace app for the entire domain.
  2. 2Admin selects which Google Chat spaces to connect.
  3. 3ClarityLift subscribes to Google Chat events via the Pub/Sub event channel.
  4. 4Events for connected spaces flow to the classifier through the same DM gate, consent gate, and aggregate-signal path as Slack and Teams.
  5. 5No Gmail content, Google Drive content, or Google Meet content is ingested in V1.

What ClarityLift does NOT read on Google Workspace

The privacy posture is led by what is excluded, not what is included.

  • Direct messages between individuals — never read, ever.
  • Group DMs — out of scope by design.
  • Channel content from teams below the 10-member group floor.
  • Personal account content of any kind.
  • Gmail — explicitly out of scope. ClarityLift does not request Gmail scope.
  • Google Drive content — out of scope.
  • Google Meet recordings, transcripts, captions — out of scope.
  • Google Chat 1:1 DMs — out of scope.
  • External-organization spaces shared into the workspace.

Retention

No message text is persisted. Aggregate signals only. Same retention posture as Slack and Teams.

Privacy considerations specific to Google Workspace

  • Google Workspace Marketplace publication requires Google security assessment for sensitive scopes — ClarityLift requests only the readonly Chat scopes, avoiding the heavyweight assessment trigger.
  • Google admin policies (data regions, retention rules) flow through normally; ClarityLift adds nothing.

What the customer does at install time

  1. 1.Workspace admin installs the Marketplace app.
  2. 2.Admin selects spaces to connect.
  3. 3.Admin sets the org-wide consent mode.

Google Workspace is on the roadmap — start with Slack or Teams today.