Skip to content
Merged
Show file tree
Hide file tree
Changes from 1 commit
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
4 changes: 4 additions & 0 deletions modules/get-started/pages/whats-new-cloud.adoc
Original file line number Diff line number Diff line change
Expand Up @@ -27,6 +27,10 @@ Serverless clusters now support up to 100 Redpanda Connect pipelines and 100 MCP

== March 2026

=== RBAC UX enhancements
Comment thread
micheleRP marked this conversation as resolved.
Outdated

Organization admins can now xref:security:authorization/rbac/rbac.adoc#service-account-roles[assign scoped roles to service accounts], restricting access to specific resource groups or clusters instead of granting organization-wide permissions.

=== Redpanda Connect updates

* Inputs:
Expand Down
19 changes: 16 additions & 3 deletions modules/security/pages/authorization/rbac/rbac.adoc
Original file line number Diff line number Diff line change
Expand Up @@ -25,13 +25,13 @@ After reading this page, you will be able to:

== Manage organization access

In the Redpanda Cloud Console, the *Organization IAM* page lists your organization's existing users and service accounts and their associated roles. You can edit a user's access, invite new users, and create service accounts. When you add a user, you define their permissions with role binding. Service accounts are assigned the Admin role for all resources in the organization.
In the Redpanda Cloud Console, the *Organization IAM* page lists your organization's existing users and service accounts and their associated roles. You can edit a user's access, invite new users, and create service accounts. When you add a user, you define their permissions with role binding.

On the *Organization IAM - Users* page, select a user to see their assigned roles. For example, for a user with Admin access on the organization, the user's _Resource_ is the organization name, the _Scope_ is organization, and the _Role_ is Admin.

Various resources can be assigned as the scope of a role. For example:
Various resources can be assigned as the scope of a role. For example:

- Organization
- Organization
- Resource group
- Network
- Network peering
Expand All @@ -44,6 +44,19 @@ Users can have multiple roles, as long as they are each for a different resource

When you delete a role, Redpanda removes it from any user or service account it is attached to, and permissions are revoked.

=== 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.
Comment thread
micheleRP marked this conversation as resolved.
Outdated

To change a service account's role:

. In the left navigation menu, select *Organization IAM*.
. Select the *Service account* tab.
. Click the edit icon for the service account you want to modify.
. Assign the appropriate role and scope.

You can only assign a service account to scopes that you have permissions for. For example, if you have the Admin role for a specific resource group, you can create a service account scoped to that resource group.

== Predefined roles

include::security:partial$predefined-roles.adoc[]
Expand Down