Skip to main content
Sync data from Google Workspace (Calendar, Drive, Chat, etc.).
Connect Parable to Google Workspace for directory, Gmail, Calendar, Drive, Meet, Chat, and audit data using the Admin SDK and related APIs.

Directory

Users, groups, organizational units

Profile photos

A member’s directory photo is their profile photo in this Workspace unless they uploaded their own. It takes the place of the photo captured at Google sign-in. Parable reads it from the Workspace’s identity data after each identity run and links to Google’s URL; it does not copy the image or look it up when a page loads. A member who leaves the directory loses the photo with the next run.

Audit & Reports

Admin audit logs, usage reports, login activity
Info: Parable reads Google Workspace data (directory, Gmail, Calendar, Drive, Meet, Chat, and related APIs). You still use Google Cloud Console to create the service account, enable APIs, and download the JSON key — that split is normal for Workspace integrations.

Data streams

This Provider Plugin defines 30 data streams.users reads every user of the domain, suspended users included, and marks a user that a later read does not return as deleted. The streams that read each user’s Gmail, Calendar, Drive, Meet, and Chat data skip a suspended user.thread_messages.labelIds holds label IDs, not names. Gmail gives a user label an ID such as Label_12, and the ID is unique only inside one mailbox. The labels stream reads each mailbox’s labels with their names, with one request per mailbox on each sync. Join labelIds to labels.id on the same primaryEmail to get the names.workspace_drive_files reads the files each user owns in My Drive. The four shared drive streams read shared drives, and they are off by default:
  • shared_drives and shared_drive_members read every shared drive and its members as the admin email, with domain administrator access.
  • shared_drive_files reads the Google Docs, Sheets, and folders of each drive as one manager of that drive, because Google lists a shared drive’s items only to its members. Parable uses the first manager in the drive’s members list who is a user and whose account is not deleted.
  • shared_drive_file_permissions reads the permissions of each item that is shared beyond its folder or drive. Google returns no permissions with shared drive items, so this stream sends one request for each such item on every sync.
Each stream reads the whole shared drive again on every sync, and marks a drive, member, item, or permission that a later read does not return as deleted. Source permissions give each item the members of its drive, the people its folders are shared with, and the people it is shared with directly. A limited-access folder and the items in it admit only the folder’s own grantees.Source permissions give each Gmail row (messages_list, threads, thread_messages, and labels) to the owner of its mailbox only: the user whose primaryEmail Parable acts as. Message headers give no access. A person named in To or Cc reads their own copy of the message, from their own mailbox, and not the sender’s copy. Each chrome_activity and gemini_activity event admits the user in actor.email only. An event with no actor email admits nobody. A person with All data access, such as a Workspace Administrator, reads every row.Source permissions give each calendar_events row to the people on the event: its attendees, the members of a group that attends, its organizer, and the user whose calendar list it was read from. A guest at another company and a room admit nobody. Calendar sharing is not read, so a delegate or a person a calendar is shared with reads the event only when it was read from their own calendar list. An admitted person reads the whole event, the full guest list included. This applies after the rebuild of the table that the change queues is approved and complete. The Meet and Chat streams and the other Admin Reports streams have no source permissions, so they read all rows (Source permissions).