Clarify view vs manage permissions in Team permissions table#3475
Conversation
|
Important Review skippedAuto reviews are disabled on this repository. Please check the settings in the CodeRabbit UI or the ⚙️ Run configurationConfiguration used: Repository UI Review profile: CHILL Plan: Pro Run ID: You can disable this status message by setting the Use the checkbox below for a quick retry:
✨ Finishing Touches🧪 Generate unit tests (beta)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
m-hulbert
left a comment
There was a problem hiding this comment.
Small tweak on the naming, but LGTM otherwise.
The Team permissions table only had a "Manage API keys" row (Admin/Owner), implying Developers cannot interact with API keys at all. In fact Developers have view-only access to API keys, integrations, channel rules, queues, and all other app features. - Add explicit "View" rows for API keys, integrations, channel rules, and queues (Developer, Admin, Owner) - Add explicit "Manage" rows for integrations, channel rules, and queues (Admin, Owner only) - Add a catch-all note above the table stating Developers have view-only access to all app features, with create/edit/delete limited to admins and the account owner Resolves DX-1547 Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
9a9a6a8 to
5c2b917
Compare
Summary
Fixes the ambiguous "Manage API keys" row in the Team permissions table at
/docs/platform/account/team(DX-1547).The table previously only had a "Manage API keys" row (Admin/Owner ✓), implying the Developer role cannot interact with API keys at all. Verified behaviour: Developers have view-only access to API keys — and to all other app features (integrations, channel rules, queues, etc.) — while only Admins and the account owner can create/edit/delete.
Changes
Notes for review
-for all new rows, consistent with Billing's existing access.Resolves DX-1547
🤖 Generated with Claude Code