Consent screen

This is where a person decides. An app or agent sends them here, and they see what would be shared, on their own mail, before anything leaves.

What the person sees

• Who is asking, with facts about them: how long they’ve been registered, how many users they have, and whether they’re verified.
• What you ask for, in plain language, and the query that will run.
• A live preview on their own mail. For example, “47 of 12,304 emails would be shared”, followed by real subject lines, with everything else as black bars. Mail the person’s rules hold back looks the same as mail your query doesn’t match.
• How long access lasts, and how to revoke it.

Send someone there

Permaily hosts this screen, so there’s nothing for you to build. Asking for access returns a consentUrl. Send the person there, and they come back to your redirect address. The Quickstart shows the request.

Asking for more later

The approved query is a cap. To get mail outside it, ask for access again with the wider query. The person sees exactly what it would add, and nothing new reaches you until they approve.

Agents choose differently

An app asks for something specific, its query. An agent connected through MCP has no such request to make, so consent works the other way round. The agent starts with nothing, and the person ticks the kinds of mail it may search while the preview updates. See Remote MCP.

Revoking

Revoking is one action, and it takes effect immediately. The screen states what stops working. It also states plainly that Permaily can’t recall mail the connection already received.