Google Workspace is one of the most common entry points into TeamScore. Most organizations connect it during signup, and the integration immediately becomes the backbone of how TeamScore understands day-to-day activity across Calendar, Drive, Meet, Chat, Login, and optional email forwarding.

This guide explains what TeamScore receives from Google Workspace, how TeamScore interprets that data, and the rules that shape how Google activity appears in a user’s timeline.

For configuration details, see Connecting Google Workspace.

What TeamScore Receives Across Google Workspace

TeamScore ingests event-level metadata from several Google Workspace services. No document contents, chat text, email bodies, or sensitive payloads are ever stored.

Directory Access

TeamScore imports users from the Google Workspace domain. Updates occur automatically so new hires appear without manual setup.

Calendar Metadata

TeamScore receives event details, timestamps, attendee lists (when available), event changes, and RSVP actions. Calendar data enables TeamScore to classify time into meeting types and calendar blocks.

Google Meet Call Metadata

TeamScore receives meeting start and end times, call duration, and location (IP-based). Google does not provide full attendee lists for all calls, so TeamScore marks incomplete metadata where necessary.

Drive Activity Signals

TeamScore receives notifications when a user views, edits, renames, creates, or downloads files. Google may batch these events during continuous work sessions; TeamScore lately compacts them to reflect the real working period.

Chat Activity Signals

TeamScore receives metadata about messages sent in Chat. Message content is never captured.

Login Activity

Google notifies TeamScore when a user performs a login or re-authentication.

Optional Outgoing Email Metadata

If your domain’s email compliance rule is configured, TeamScore receives outgoing email subjects and headers. Email bodies and attachments are never received.

For more information, please refer to the Gmail Forwarding guide.

How Google Activity Appears in TeamScore

TeamScore displays Google Workspace activity using a consistent structure across services:

Calendar

Events and interactions are color-coded by type and duration. Long, personal, or non-work events may be excluded from scoring.

Meet

Calls appear with precise start and end times. Some calls may show incomplete attendee information due to Google API limits.

Drive

Frequent editing events are compressed into meaningful blocks during TeamScore’s nightly processing. Only file titles are shown.

Chat

Chat messages appear as discrete activities. Message content is never shown.

Login

Logins appear as short entries reflecting authentication behavior.

Email (Optional)

Outgoing emails appear as small entries with subject lines only.

Data Details and Privacy

TeamScore receives only metadata. TeamScore never receives email content, document contents, chat text, audio, video, or transcript data, Google Meet recordings, Drive file contents or attachment data.

TeamScore’s purpose is transparency, not inspection. The integration is intentionally scoped to visibility signals rather than content.

Notes of Data Processing

Google may generate system-level events overnight (e.g., room creation, automated adjustments). TeamScore’s nightly process identifies and suppresses redundant or noisy events so timelines remain accurate and readable.

Drive editing sessions and repeated calendar adjustments are compressed to reflect meaningful blocks of work rather than raw notification volume.

Domain Requirements

Each Google Workspace domain can be connected once.

If an organization manages multiple domains, each domain can be added, but duplicate connections to the same domain are blocked to avoid unnecessary parallel processing.