Google Calendar and Outlook Calendar open Calendar’s existing Settings → Calendar → Integrations panel. Standard workspace permissions and provider consent apply.
Gmail and Outlook Mail open Mail settings → Accounts in the personal workspace. New connections and reconnects are in internal early access while the provider setup is in progress. Mail checks staff access before issuing OAuth state and checks it again before completing OAuth. Both checks use the current, subject-bound Auth record and the same verified staff policy as Meet vanity links. Unconfirmed addresses, subdomains, lookalike domains, and designated QA identities do not qualify. Azure-linked staff identities must also satisfy the configured directory policy.
Existing connected mailboxes can still be read, used, or disconnected under the existing account and workspace ownership checks. Mail and Calendar request provider consent independently.
Google Workspace and Microsoft 365 describe suite-wide integrations in the catalog. Their Mail and Calendar connectors are listed separately. Discord workspace administration and operator-maintained Discord, Zalo, or WhatsApp channels are separate from the catalog’s self-service connection flows.
The catalog reserves the exact
/integrations URL and its localized forms. A workspace with a pre-existing integrations handle can use its UUID-based workspace URL. Workspace subpaths still require their normal access checks.
Coverage lives in apps/mail/src/lib/mail/auth.test.ts, apps/mail/src/lib/mail/connected/route.test.ts, and apps/mail/src/app/api/v1/mail/connected/callback/route.test.ts.