In your workspace, choose Connections, pick Gmail, and sign in through Google's own consent flow. flo.space never sees your password; Google shows you exactly which scopes are requested before anything is granted.
The scopes, plainly. At connection: reading messages and threads, which is what lets drafts carry real context. That is all; nothing at this stage can send, delete, or modify mail. If you later enable sending, a second explicit grant adds creating and sending drafts, and even then every individual message waits for your approval in the queue.
Google Workspace accounts. If your organization restricts third-party apps, the connection will pause at Google's screen until a Workspace admin allow-lists flo.space (Admin console → Security → API controls). It is a two-minute setting; send your admin the security page, which documents the scopes and the control model.
To revoke: disconnect from flo.space settings, or remove the app from your Google account's security page; either works instantly and independently. Working context already prepared is deleted on disconnect per the privacy policy.
Once connected, expect the first drafted replies within a day. If nothing appears, see actions not appearing.
