Can OrgOrg build an org chart from Google Workspace?

Yes. The Directory connection reads each account's manager field and draws the reporting lines. A change in Workspace reaches the chart on the next sync, and a new account appears the day it is created. The chart needs no drawing and no upload.

Which Google scopes does OrgOrg ask for?

Each tile asks for its own. The directory tiles read users, org units, and the customer record. Calendar reads and writes events, and Groups reads and writes memberships. Contacts is read-only, Drive takes drive.file, the narrowest Drive scope, and Gmail takes metadata, with readonly only for content sync. An unused tile asks for nothing.

Does the sync go both ways?

The directory sync does: a photo or a title edited in OrgOrg goes back to Workspace, and a change in Workspace comes to OrgOrg. Groups follow the roster rule in OrgOrg. Contacts and Gmail metadata are read-only.

Is Google Workspace required?

No. Microsoft 365 connects the same way, with its own directory, calendar, and mail tiles, and Gusto or Rippling can provision the people instead. A person who exists in two sources is one profile, matched by email.

Integration

Google Workspace org chart and directory sync, with calendar, groups, and sign-in

The Google Workspace integration reads your directory into OrgOrg. Each account becomes a profile, the manager field draws the org chart, and a new hire appears the day their account does. Calendar, Groups, Contacts, Drive, and Gmail connect on top, each with its own grant and the narrowest scope.

What connects

Directory: profiles, photos, and manager lines sync both ways, and user provisioning follows the Workspace account.
Calendar: booking links, team calendars, and time-off visibility read the calendars people already keep.
Groups: a roster rule keeps a Google Group's membership current.
Contacts: CRM contact enrichment for every member, read-only.
Drive: Docs, Slides, Sheets, and Drawings exports for every member.
Gmail: email metadata for CRM signals, and content sync for the CRM records you choose.
Sign-in: Google sign-in for every member, with the verified email as the identity.

The apps that use it

How to set it up

Connect the directory. In OrgOrg, go to Settings, then Connectors, and click Connect on the Directory tile. A Workspace admin grants the directory scopes once, for the whole domain.
Watch the profiles fill. Each account becomes a profile with its name, photo, title, and manager. The org chart draws from the manager field.
Add the grants you use. Calendar, Groups, Contacts, Drive, and Gmail are separate tiles, each with its own scopes. Connect only the ones an app needs.
Map the groups. Map a roster to a Google Group, and the group's members follow the rule as the directory changes.

The permissions it asks for

Permission	What OrgOrg does with it
admin.directory.user.readonly, admin.directory.orgunit.readonly, admin.directory.customer.readonly	The Directory tile reads the users, the org units, and the customer record, to build the profiles and the org chart.
calendar	The Calendar tile reads and writes events for booking pages, team calendars, and 1:1s.
admin.directory.group, admin.directory.group.member, cloud-identity.groups	The Groups tile reads and writes group membership, so a roster can keep a Google Group current.
contacts.readonly	The Contacts tile reads contacts to enrich CRM records. It writes nothing.
drive.file, with spreadsheets and presentations as options	The Drive tile touches the files OrgOrg creates or the person opens with it, never the whole drive.
gmail.metadata, with gmail.readonly as an option	The Gmail tile reads message metadata for CRM signals, and the content of the threads you file to a record.

See OrgOrg plansFree for teams of up to five, every integration included.

Frequently asked questions

Can OrgOrg build an org chart from Google Workspace?: Yes. The Directory connection reads each account's manager field and draws the reporting lines. A change in Workspace reaches the chart on the next sync, and a new account appears the day it is created. The chart needs no drawing and no upload.
Which Google scopes does OrgOrg ask for?: Each tile asks for its own. The directory tiles read users, org units, and the customer record. Calendar reads and writes events, and Groups reads and writes memberships. Contacts is read-only, Drive takes drive.file, the narrowest Drive scope, and Gmail takes metadata, with readonly only for content sync. An unused tile asks for nothing.
Does the sync go both ways?: The directory sync does: a photo or a title edited in OrgOrg goes back to Workspace, and a change in Workspace comes to OrgOrg. Groups follow the roster rule in OrgOrg. Contacts and Gmail metadata are read-only.
Is Google Workspace required?: No. Microsoft 365 connects the same way, with its own directory, calendar, and mail tiles, and Gusto or Rippling can provision the people instead. A person who exists in two sources is one profile, matched by email.