OAuth, without the surprise permissions
We're rolling out a first-class authorization flow for third-party apps — so when an integration asks for access to your account, you see exactly what it wants before you say yes.
Every integration story starts the same way: a user pastes an API key into a tool they barely trust, or worse, hands over their password. We've watched enough of these go sideways — revoked keys, over-scoped access, mystery scripts running against production — to know the pattern needed to end.
So we built a proper OAuth authorization flow. When a third-party app asks to act on your behalf, you land on a page that shows you who's asking and what they want, and you decide Authorize a Third-Party App.
Why a dedicated authorization page
The temptation with OAuth is to treat the consent screen as a formality — a checkbox between the developer and the token. That's how you end up with users who don't remember granting anything and support tickets that start with "why does this app have access to my data?"
We wanted the opposite: a page whose entire job is to make the grant explicit. It loads when a third-party app requests access, it names the app, and it doesn't do anything until you actively approve Authorize a Third-Party App. If you close the tab, nothing happens. That's the whole design goal — no ambient permissions, no drive-by grants.
What this unlocks
For developers, this is the missing piece for building integrations that don't require users to generate long-lived tokens by hand. You send users to the authorization page, they approve, you get a scoped grant back. Standard OAuth, but ours.
For everyone else, it means the ecosystem of tools that plug into your account can grow without each new integration being a small trust exercise. The prompt is the same shape every time, from every app, so "do I trust this?" becomes a decision you can actually make quickly instead of a wall of unfamiliar UI.
What's next
This is the foundation. Next up: finer-grained scopes, a dashboard for reviewing and revoking apps you've previously authorized, and better signals on the consent screen itself — verified publishers, usage history, the kind of context that makes the decision easier the tenth time as well as the first. If you're building an integration and want early access to the developer side, let us know.