Table of contents
Google Workspace Integration Overview
Google Workspace is the most common entry point into WorkSights. Most organizations connect it during signup, and it immediately becomes the backbone of day-to-day visibility across Calendar, Drive, Meet, Chat, Login, and optional email forwarding.
This guide covers what WorkSights receives from Google Workspace, how that data is interpreted, and the rules that shape how Google activity appears in each user's timeline.
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. Updates sync automatically so new hires appear without manual setup.
Calendar
WorkSights receives event details, timestamps, attendee lists (when available), event changes, and RSVP actions. Calendar data lets WorkSights classify time into meeting types and calendar blocks.
Meet
WorkSights receives meeting start and end times, call duration, and IP-based location. Google does not provide full attendee lists for all calls, so WorkSights marks incomplete metadata where applicable.
Drive
WorkSights receives notifications when a user views, edits, renames, creates, downloads, or shares a file. Google may batch these events during continuous work sessions. WorkSights compacts them during nightly processing to reflect the real working period.
Chat
WorkSights receives metadata about messages sent in Google Chat. Message content is never captured.
Login
Google notifies WorkSights when a user performs a login or re-authentication.
Email (Optional)
If your domain's email compliance rule is configured, WorkSights receives outgoing email subjects and headers. Email bodies and attachments are never received. See the Gmail Forwarding guide for setup details.
How Google Activity Appears in WorkSights
WorkSights displays Google Workspace activity using a consistent structure across services.
Calendar: Events are color-coded by type. Internal meetings, external meetings, and calendar blocks each use a distinct color. Events longer than ten hours are excluded from scoring.
Meet: Calls appear with actual start and end times. Some calls may show incomplete attendee information due to Google API limits.
Drive: Repeated editing events on the same file are compacted into a single block during nightly processing. Only file titles are shown.
Chat: Messages appear as discrete activity entries. Message content is never shown.
Login: Login events appear as short one-minute entries reflecting when a user authenticated.
Gmail (Optional): Outgoing emails appear as small entries with subject lines only.
Data Processing
WorkSights receives only metadata. Email content, document contents, chat text, audio, video, recordings, and transcript data are never received or stored.
Google generates some system-level events overnight, such as automated room additions and calendar adjustments. WorkSights's nightly processing identifies and suppresses these so timelines stay accurate.
Drive editing sessions and repeated calendar changes are compacted to reflect meaningful work blocks rather than raw notification volume.
Domain Requirements
Each Google Workspace domain can be connected once. If an organization manages multiple domains, each can be added separately. Duplicate connections to the same domain are blocked to prevent redundant processing.
Troubleshooting
If Google Workspace activity is not appearing as expected:
- Confirm the Google Workspace domain connection is active in Settings under Connected Services.
- Check that the affected user exists in the WorkSights user list and has been assigned a role.
- Verify that the relevant service (Calendar, Drive, Meet, Chat) is enabled in service-level controls.
- Gmail activity requires a separate forwarding rule. If email entries are missing, see the Gmail Forwarding guide.
- For persistent issues, contact support via the in-app chat.