bluesky-social/atproto

PDS: review existing oauth scopes via connected apps list

Closed

#4,838 opened on Apr 7, 2026

 (2 comments) (5 reactions) (0 assignees)TypeScript (868 forks)github user discovery
enhancementgood first issueoauth

Repository metrics

Stars
 (9,441 stars)
PR merge metrics
 (PR metrics pending)

Description

Scenario I want to stay on top of which apps are messing with what in my PDS. To do so, it's not enough to just make a granular Goldilocks decision once per app. (The more apps I use, the fewer details I can remember.)

Solution PDS-level account management needs a friendly "apps" page, so people can:

• list all authorized apps • see what each can do (1 click) • revoke oauth access to any (2 clicks)

Where the list page is bog-simple, + the details page matches the original authorize screen.

Existing UX The current https://bsky.social/account implementation directly connects the first + last of these:

There are a few glaring flaws to sort out (#4278, #4424), but overall it's quite nice.

Recommended UX Add one-click access for more details, using the summary/detail panel of permissions originally granted on the Authorize screen:

Additional wordsmithing needed, + usability testing may reveal ways to streamline this even further. But you get the idea -- the details panel here should rhyme as closely as possible to how it's used on the Authorize screen.

Other alternatives considered Note that this flow focuses on apps first, then repositories. People may someday want an "advanced" mode to invert (or filter) that, so they can instead ask:

"which apps did I authorize to mess with this repo?"

If anyone wants to work on designs for that, open a new issue.

Contributor guide