App login and mailbox authorization

The signed-in application user and connected Gmail mailbox are separate identities. Google login does not grant administrator access or replace Gmail consent. Configure both through Google Cloud setup.

The actor is the app user that requests an operation. The connected account binds that actor to an internal mailbox UUID and verified Google subject. The mailbox queue uses its mailbox user ID, not the login email or Google email address.

A grant records allowed access. Examples include a MailGen model permission or Google consent for mailbox scopes. A credential source identifies the verified OAuth grant or delegated Workspace authority used for that mailbox. Its policy controls whether that source remains valid and which provider operations it supports. Neither is the actor's personal content-encryption key. See identity concepts.

New operations require an active connection visible to the actor and current permission. Durable execution checks saved signed proof of the accepted action, called an admission. It also checks the original provider/source binding. See background-work terms. Execution also checks current mailbox visibility and the same credential source. Source revocation or an invalid proof can block execution. A later group change alone does not erase valid admission for already accepted work.

If login works but mail does not load, inspect separate mailbox consent and onboarding status. Read ordered recovery before retrying an uncertain write.