Table of contents
Google Workspace Integration Overview
Google Workspace is the broadest WorkSights integration. A single org-level connection made by a Workspace admin covers the entire domain, bringing Calendar, Drive, Meet, Chat, and Login activity into the timeline, plus optional outgoing email metadata through a separate forwarding rule.
Activity comes from Google’s Admin audit logs, delivered in near real time. No document contents, chat text, email bodies, or recordings are ever received.
For connection steps, see Connecting Google Workspace.
What WorkSights Receives
WorkSights ingests event-level metadata from several Google Workspace services. No document contents, chat text, email bodies, or sensitive payloads are ever stored.
Directory
WorkSights imports users from the Google Workspace domain and keeps the list current as people join. This drives user mapping across every Google Service.
Calendar
Events details, timestamps, attendee lists, event changes, and RSVP actions. Calendar data lets WorkSights classify time into meetings and focus blocks.
Drive
Notifications when a user views, edits, creates, renames, moves, shares, downloads, or comments on a file. Only file titles and action types are received, never document contents.
Meet
Call start and end times and each participant’s real attendance duration, recorded when a call ends.
Chat
Metadata about messages, rooms, and threads. Message content is never received.
Login
Authentication events, including successful logins, failed attempts, and login challenges, with network and region information.
Email (Optional)
If your domain’s forwarding rule is configured, WorkSights receives outgoing email header metadata: subject, participants, and attachment names, never the body. See the Gmail Forwarding guide for setup.
How Google Activity Appears
Calendar events are categorized by type. An event resolving to a single relevant participant is a Calendar Block, used for focus time. An event with two or more participants who are all internal is a Meeting (Internal). An event with any external participant is a Meeting (External). Rooms and equipment are ignored when applying this rule, and the category is re-evaluated whenever guests change, so adding an external guest can flip a meeting from internal to external. Events longer than ten hours are excluded from scoring.
Because a meeting is written for the organizer, the actor, and the calendar owner, the same meeting can legitimately appear on several people’s timelines, provided each has an active subscription.
Meet calls appear once per participant, each reflecting that person’s real attendance time rather than the scheduled slot. Calls appear after they end, not while in progress.
Drive activity appears with the file title and action. Repeated edits to the same file within a working session are consolidated into a single block reflecting the real working period, rather than one entry per notification.
Chat activity appears as discrete entries showing the action and room. Login events appear as short entries marking each authentication.
Integration Page Overview
The Google Workspace integration page contains:
- Overview - Connection details and integration owner
- Users - Directory users mapped to WorkSights users
- Features - Service-level controls for Calendar, Drive, Meet, Chat, and Email
- Connections - Connected Google Workspace domains
Data Notes
WorkSights receives metadata only. Email content, document contents, chat text, audio, video, recordings, and transcripts are never received or stored.
Google generates some system-level events overnight, such as automated room additions. WorkSights identifies and suppresses these so timelines stay accurate. Working-location calendar events are ignored entirely.
For Drive, Chat, and Meet, activity from someone who resolves to a known client contact rather than a mapped user is stored as client-authored activity on ClientSights, giving relationship context without affecting scores.
Domain Rules
Each Google Workspace domain connects once. Organizations managing multiple domains can add each separately. Duplicate connections to the same domain are blocked to prevent redundant processing.
Troubleshooting
No activity after connecting
Confirm the provisioning wizard was completed and the affected user is mapped to a WorkSights user with an active feature subscription for the relevant service. Unmapped actors are skipped.
Activity stopped for everyone at once
The admin token may have been revoked, for example if the connecting admin left, reset their password, or withdrew consent. This stops all Google activity together. Have a Workspace admin reconnect Google.
Activity stopped for one service only
A watch channel may have expired without renewing. The next processing cycle repairs the gap automatically. If it persists, reconnecting refreshes all channels. Contact us at success@worksights.ai for assistance.
A meeting appears on several people’s timelines
This is expected. A meeting is written for the organizer, the actor, and the calendar owner, each of whom has an active subscription.
Activity appears late
This is expected. Activity is processed in batches roughly every 10 to 15 minutes.
A non-admin tried to connect
Google’s directory and audit scopes require an admin account. Reconnect with a Google Workspace admin.