Connected Apps Settings
Ruled list of OAuth apps with scope badges, connected date, authorizing member, and an instant Revoke action per row.
Ruled list of OAuth apps with scope badges, connected date, authorizing member, and an instant Revoke action per row.
The Application Collection unlocks the source for every Application block. All Access unlocks every Collection.
Already purchased? Log in
Connected Apps Settings is the OAuth integrations panel, five ruled rows for GitHub (repo:read, repo:write, webhook:write connected by Avery Stone on Mar 4, 2026), Slack, Figma, Jira, and Linear, each showing the app name, a plain description of what it can do, scope badges, the connected date and the team member who authorized it, and a Revoke button. The footer carries the honest line: revoking is instant and the app loses access on its next request, not its next login.
Apps are one const array; the scope badges use the secondary variant so they read as metadata rather than status. The authorized-by field matters because revoking someone else's integration is a conversation, not a click.
Reach for this block on the security or integrations tab of a settings shell, wired to your OAuth grants endpoint. The Revoke button should call a server action and remove the row optimistically.
A natural flow around it on an Application Pro page:
Before
After
One strong use is the workspace OAuth audit list. Other variants:
Tip: showing who authorized an app is half the audit log; without it no admin knows whether a revoke is safe.