Page MenuHomePhabricator

[UI/UX] Programmatically enforce restrictions on updating grants for auth-only accepted consumers
Open, Needs TriagePublic

Description

This caused T413947 and T409901, so we should probably find a way to restrict users from updating grants for auth-only OAuth2 consumers.

At the moment, a user can force access to the "manage grants" page even when it's not displayed when viewing the connected apps list. See sample images below;

Screenshot 2026-01-07 at 7.00.47 PM.png (1×3 px, 483 KB)
Screenshot 2026-01-07 at 6.59.51 PM.png (1×3 px, 432 KB)

Event Timeline

OTOH without access to that screen, they can't even see what grants the application has. I think the link should be unconditional, and then maybe there shouldn't be an update button if no meaningful changes can be made.

OTOH without access to that screen, they can't even see what grants the application has. I think the link should be unconditional, and then maybe there shouldn't be an update button if no meaningful changes can be made.

Yes, this makes sense. I think this should also extend to non-authonly consumers that have only basic rights as well?

There seems to be an overlap between "authonly" consumers (authonly and authonlyprivate) and "non-authonly" consumers with only basic rights (useoauth). The overlap is that these are the default rights applied, and I'm wondering if it would make sense to also not have access to the "Update grants" button in the latter case. So I'm thinking of unifying the experience of these management workflows.

But for consumers who have more grants (outside the defaults), we can display the "Update grants" button for grant management. Let me know what you think.