Table of contents
Google Workspace is one of the most common entry points into WorkSights. Most organizations connect it during signup, and the integration immediately becomes the backbone of how WorkSights understands day-to-day activity across Calendar, Drive, Meet, Chat, Login, and optional email forwarding.
This guide explains what WorkSights receives from Google Workspace, how WorkSights 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 WorkSights Receives Across Google Workspace
WorkSights ingests event-level metadata from several Google Workspace services. No document contents, chat text, email bodies, or sensitive payloads are ever stored.
Directory Access
WorkSights imports users from the Google Workspace domain. Updates occur automatically so new hires appear without manual setup.
Calendar Metadata
WorkSights receives event details, timestamps, attendee lists (when available), event changes, and RSVP actions. Calendar data enables WorkSights to classify time into meeting types and calendar blocks.
Google Meet Call Metadata
WorkSights receives meeting start and end times, call duration, and location (IP-based). Google does not provide full attendee lists for all calls, so WorkSights marks incomplete metadata where necessary.
Drive Activity Signals
WorkSights receives notifications when a user views, edits, renames, creates, or downloads files. Google may batch these events during continuous work sessions; WorkSights lately compacts them to reflect the real working period.
Chat Activity Signals
WorkSights receives metadata about messages sent in Chat. Message content is never captured.
Login Activity
Google notifies WorkSights when a user performs a login or re-authentication.
Optional Outgoing Email Metadata
If your domain’s email compliance rule is configured, WorkSights 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 WorkSights
WorkSights 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 WorkSights'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
WorkSights receives only metadata. WorkSights never receives email content, document contents, chat text, audio, video, or transcript data, Google Meet recordings, Drive file contents or attachment data.
WorkSights'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). WorkSights'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.