Google Integration

What this section is for

Google Integration wires teams up to Google Workspace. When you join a team, the app grants you access to that team's Google Group and any linked Shared Drive folders or files; leaving revokes it. Admins can also provision a @nobodies.team Workspace account for any human, and the app monitors Drive folders for permission changes made outside the system.

This section covers the sync mechanics, drift detection, and admin tools. For the human-facing side of email — using your @nobodies.team mailbox, sending from a group address, the inbox setup — see Email.

All Drive resources are on Shared Drives only (no personal My Drive), and the app manages only direct permissions — inherited Shared Drive permissions are left alone. Sync is mode-gated per service: an Admin must switch Google Drive and Google Groups from None to AddOnly or AddAndRemove before any job or manual sync will modify Google. See sync mode and reconciliation for definitions.

Key pages at a glance

Google dashboard (/Google) — entry point; on-demand check buttons (Sync System Teams, Check Group Settings, Check Email Renames). Sub-pages (sync settings, accounts, domain groups, outbox, detection results) are reached from the Google section of the admin sidebar.
Sync status (/Google/Sync) — tabbed Drive / Groups view of every active linked resource with drift and Sync Now.
Sync settings (/Google/SyncSettings) — per-service sync mode (None / AddOnly / AddAndRemove).
All Groups (/Google/AllGroups) — every Google Group in the domain, linked or not.
Workspace accounts (/Google/Accounts) — every @nobodies.team account, with link-to-human search.
Sync audit — per-human (/AuditLog/Human/{id}) and per-resource (/AuditLog/Resource/{id}).
Team resources (/Teams/{slug}/Resources) — where coordinators link, unlink, and sync a team's Drive folders, files, and Groups.
Drive activity — anomalous changes land in /AuditLog under the "Anomalous Permissions" filter.

As a Volunteer

Why you may have a `@nobodies.team` account

An admin can provision a @nobodies.team account for you. You get a credentials email at your personal address — username, temporary password, sign-in link — and on first login you must change the password and set up 2FA. That address then becomes your Google service email (the app's service account uses it to add you to Groups and Shared Drive folders for every team). Until provisioning happens, your OAuth login email is used instead.

For how to use the mailbox itself, set up two-factor auth, and send "as" your team's group address, see Email.

Set or change your Google service email

Go to Profile → Emails and verify the address you want Google to know about. Changing it resets your sync status to Unknown and re-queues access for every team. If Google permanently rejects an address, your status is set to Rejected and the app stops trying — fix it on the Emails page to reset.

![TODO: screenshot — Profile Emails page showing the verified Google service email with notification-target toggle]

What access you get automatically

Joining a team grants you its Group membership and writer access to its linked Shared Drive folders and files on the next sync; leaving revokes it. Sub-team members also get parent-department resources — rolled up one way (department members do not get sub-team resources).

Email — the human-facing side of @nobodies.team mailboxes and group addresses.
Teams — membership drives Group and Drive access; resource linking lives on the team admin page.
Profiles — set your Google service email on the Emails tab.
Glossary — service account, Shared Drive, sync mode, reconciliation.