Setup journey
Identity, product authority, and provider data are confirmed in separate, transparent steps so one connection never becomes blanket access.
Step 01
CFO, Marketing, Organic, and Operator carry different constitutions and authority boundaries. Connector access follows the selected product; it does not define it.
Google OpenID Connect confirms the person authorizing the business. Good Productivity validates the signed identity, verified email, and tenant membership before any product grant is issued.
This identity step does not authorize Analytics, Drive, Calendar, or another Google product.Each connection opens its own pre-consent disclosure. You see the data families, access level, product purpose, offline access, and how to disconnect before leaving Good Productivity for the provider’s consent screen.
Google measurement is read-only. Other providers keep their own independent permissions.Use the canonical resource in ChatGPT, Codex, Claude, or Claude Code. The client opens the secure authorization flow and receives only the tenant, product, scopes, connections, and assets included in the approved grant.
No provider token is copied into chat or placed in an MCP argument.Choose your AI workspace
One accountable flow
Good Productivity keeps the founder identity, OS authority, provider permissions, selected assets, and AI-client access visible as separate layers. No password or provider secret belongs in a prompt.