Conversation
…ping - Remove incorrect statement that service accounts are always assigned org-wide Admin role - Add Service account roles section documenting scoped role assignment - Add RBAC UX enhancements entry to What's New (March 2026) Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
✅ Deploy Preview for rp-cloud ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
📝 WalkthroughWalkthroughThis PR updates documentation to reflect RBAC user experience improvements. Release notes are updated to announce that organization admins can now assign scoped roles to service accounts, restricting access to specific resource groups or clusters. The RBAC authorization documentation is concurrently updated to remove outdated information stating service accounts are always assigned organization-wide Admin roles, and adds a new "Service account roles" section with step-by-step UI instructions for editing service account roles via the Organization IAM interface, along with clarification that scoping options are limited to the current admin's permissions. Estimated code review effort🎯 2 (Simple) | ⏱️ ~10 minutes Possibly related PRs
Suggested reviewers
🚥 Pre-merge checks | ✅ 3✅ Passed checks (3 passed)
✏️ Tip: You can configure your own custom pre-merge checks in the settings. ✨ Finishing Touches📝 Generate docstrings
🧪 Generate unit tests (beta)
Comment |
![coderabbitai[bot]](https://avatars.githubusercontent.com/in/347564?s=60&v=4){kind=small}
There was a problem hiding this comment.
🧹 Nitpick comments (1)
modules/security/pages/authorization/rbac/rbac.adoc (1)
28-28: Small wording cleanup for RBAC terminology consistency.Line 28 reads a bit awkwardly with singular “role binding”; consider “with role bindings” for consistency with the rest of the page.
🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed. In `@modules/security/pages/authorization/rbac/rbac.adoc` at line 28, Update the sentence on the Organization IAM page that currently ends "...When you add a user, you define their permissions with role binding." to use the plural form for consistency; edit the text in rbac.adoc replacing "role binding" with "role bindings" so it reads "...define their permissions with role bindings." Ensure the change is applied to the string in the Organization IAM paragraph containing "When you add a user, you define their permissions" to keep RBAC terminology consistent across the page.
🤖 Prompt for all review comments with AI agents
Verify each finding against the current code and only fix it if needed.
Nitpick comments:
In `@modules/security/pages/authorization/rbac/rbac.adoc`:
- Line 28: Update the sentence on the Organization IAM page that currently ends
"...When you add a user, you define their permissions with role binding." to use
the plural form for consistency; edit the text in rbac.adoc replacing "role
binding" with "role bindings" so it reads "...define their permissions with role
bindings." Ensure the change is applied to the string in the Organization IAM
paragraph containing "When you add a user, you define their permissions" to keep
RBAC terminology consistent across the page.
ℹ️ Review info
⚙️ Run configuration
Configuration used: Organization UI
Review profile: CHILL
Plan: Pro
Run ID: 58004069-4ca9-470e-915b-99876d255e9c
📒 Files selected for processing (2)
modules/get-started/pages/whats-new-cloud.adocmodules/security/pages/authorization/rbac/rbac.adoc
|
|
||
| === Service account roles | ||
|
|
||
| By default, new service accounts are assigned the Admin role at organization scope. You can edit a service account to assign a different role or restrict the scope to a specific resource group or cluster. |
There was a problem hiding this comment.
This is not correct. When you create a service account, you also create the role bindings; nothing is created by default:
As you see, you provide the name, description, and then set the role bindings you need
There was a problem hiding this comment.
Thanks Mateo, I've updated the page
|
|
||
| == March 2026 | ||
|
|
||
| === RBAC UX enhancements |
There was a problem hiding this comment.
This is correct, but has been like that since around June last year
There was a problem hiding this comment.
I've removed from What's New
2 participants
Summary
This pull request updates the Redpanda Cloud RBAC documentation to clarify role and role binding concepts, improve instructions for managing organization access, and provide clearer guidance on predefined roles. The changes focus on making the documentation more accurate, user-friendly, and consistent.
Addresses DOC-1864 / ENG-793.
Deploy preview links
Test plan
npm run buildpasses with no new errors or warnings🤖 Generated with Claude Code