google.

this connector is the account: the Google address, its token, its default account. since the 2026-09-26 split, each service — Gmail, Drive, Sheets, Calendar, Tasks, Chat, BigQuery — is a connector in its own right, with its own consent (its scopes only): authorise them from their card, one by one, on the same account.

an organization admin (Org tab) or a team lead (Team tab) can connect ONE Google account on behalf of everyone — a shared mailbox, a team calendar. tools take your own account first, then your active team's, then the organization's; _account=<email> targets a specific account wherever it lives. nobody reaches another person's personal account: only what an admin has set up as shared is shared.

google_accounts — the connected accounts and, for each, the services it has authorised. this is the question to ask when a service tool refuses: the account exists but has not yet authorised THIS service.

the platform's OAuth consent screen stays in Testing mode, and that is a choice: moving to *published* with the Gmail, Drive and Chat scopes (RESTRICTED at Google) requires a paid, annual CASA Tier 2 audit. two consequences, to know before relying on it:

a partner who sets up their own Google app (tenant, /admin › OAuth apps) is not affected: their users consent under THEIR project, whose services they choose to have verified — that is what the split is for.

this connector accepts multiple comptes: connecting with another compte adds it alongside the others, named by its address; reconnecting with the same one replaces its own.