A practical guide to reading an OAuth consent screen, deciding what is reasonable, and knowing how to take it back.
Key takeaways. The consent screen is the contract. It lists specific scopes, and read and modify are very different grants. Ask three things: what does it read, what can it change, and where do the tokens live. Revocation should exist in two places — inside the product and in your Google account — and you should test it early. A vendor that cannot describe its write boundary in one sentence has not designed one.
The four seconds that matter. Connecting an app to Google is one of the shortest and most consequential interactions on the internet. A screen appears, it lists some permissions in language written by neither party, and there is a blue button. Most people read the app name and press it. The screen is worth four more seconds, because it is the actual contract. Everything the tool can ever do with your mail is on it, and nothing that is not on it is possible without asking you again.
Read the verbs, not the product name. Google groups permissions into scopes, and the meaningful difference between them is the verb. Read. The app can see the content. For Gmail that means message bodies and history; for Calendar, every event on every calendar; for Tasks, all lists and items. This is the grant that makes an agent useful at all, and it is also the broadest thing you will hand over. Modify or write. The app can change things — create a draft, edit an event, complete a task. This is what lets a tool act rather than describe, and it is the one to be deliberate about. Send. Specifically the ability to put a message in front of another person. Worth treating as its own category, because it is the only one on this list whose mistakes are visible to somebody else. Metadata only. Headers and labels without bodies. Rare, and a genuinely good sign when you see it, though it limits what the tool can do. Scope names are unhelpfully similar and the summaries are terse. If the grant surprises you when you read it slowly, that is worth pausing on. Decline is a normal outcome, and you can always connect later.
Three questions worth asking any AI tool. The consent screen tells you what is technically possible. It does not tell you what the product will actually do, and that is a separate question with a separate answer. What does it read, and when? Continuously in the background, or only when you ask it something? Both are defensible; only one of them is what most people assume. What can it change without asking me? This is the question most product pages avoid. If there is no clear answer, the boundary has not been designed. Where do the access tokens live, and how do I revoke them? Tokens are the keys. Knowing who holds them, and having a revocation path you have actually tested, is the difference between a considered decision and a hopeful one.
How Drift answers them. Stated plainly, because a page that asks you to interrogate other vendors should answer its own questions first. Drift reads the Google surfaces you connect when it needs them to answer you — mail, calendar events and free time, and task lists, including a searchable archive of the past twelve months. Reading is what makes any of the rest work, and it happens in service of a request rather than as a constant background sweep. On writing, the rule is recoverability. Saving a draft in your own mailbox, creating or completing a task, and creating or editing a Notion page all run without interrupting you, because you can undo every one of them. Sending, replying to or forwarding an email always stops on a confirmation card that shows every recipient and the full body first. Deleting a message or a task stops too. Calendar writes are the one exception, and they include deletes. They run inline, with no confirmation card. An earlier build did ask, by pausing the turn and resuming it after approval — and because each resume was a fresh model turn, the same event was created over and over until the turn hit its tool limit. Running calendar writes in the same turn as the reads is what stopped that. It is the one place the rule bends, and it is a deliberate trade, not an oversight. On tokens: connections are authorised through Composio, Drift’s connected-account provider, using each service’s own permission flow, and the access tokens are held there rather than in Drift’s own database. Disconnect a connection in Settings and its cached projections are deleted along with it.
Revoking, and why to test it now. Two paths should always exist, and it is worth walking one of them in the first week rather than the week you need it. In the product. Drift disconnects a connection from Settings, and the cached projections for that account go with it. In your Google account. The third-party access page lists everything you have ever connected and removes access independently of whether the app cooperates. This is the one that always works. One practical note if you are on a work account: Google Workspace administrators can block third-party authorisation entirely. When that is the case the connection fails at Google rather than in the app, and only an administrator can change it.
If it requested a read scope, then technically yes — the consent screen is the boundary, and a read grant covers message bodies and history rather than a subset you choose. What a specific product actually reads, and when, is a separate promise it makes outside that screen, which is why it is worth asking directly.
Two ways. Disconnect it inside the product, which for Drift is in Settings and also deletes the cached projections for that account. Or remove it from the third-party access page of your Google account, which works whether or not the app cooperates. Test whichever path you plan to rely on before you need it.
No. Drift does not use your content to train its own models, and does not permit model providers to train on content submitted through the service where the provider offers that control. Your conversations and the connected data they need are sent to model providers only to generate the response you asked for.