Note: Doc team updates the current version of the documentation and the
two previous versions (n-2), but we address *only high-priority, or
customer-reported issues* for -2 releases in support.
Describe the changes in the doc and link to your dev story:

1. - [X] Mandatory: Add the required version to the Fix version/s field.

2. - [ ] Mandatory: Choose the type of documentation change or review.

• [X] We need to update to an existing topic

• [ ] We need to add a new document to an existing section

• [ ] We need a whole new section; this is a function not
  documented before and doesn't belong in any current section

• [ ] We need an Operator Advisory review and approval

• [ ] We need a z-Stream (Errata) Advisory and Release note for
  MCE and/or ACM

3. - [X] Mandatory: Find the link to where the documentation update
should go and add it to the recommended changes. You can either use the
published doc or the staged repo for this step:

https://docs.redhat.com/en/documentation/red_hat_advanced_cluster_management_for_kubernetes/2.15/html/secure_clusters/securing-cluster-intro#rhacm-rbac-implement
This doc update request is to update the fine-grained rbac doc for changes made in ACM 2.16 GA status that requires changes in different areas of the doc

Note: As the feature and doc is understood, this recommendation may
change. If this is new documentation, link to the section where you think
it should be placed.

Customer Portal published version

https://docs.redhat.com/en/documentation/red_hat_advanced_cluster_management_for_kubernetes/2.12

Doc staged repo within the ACM Workspace:
https://github.com/stolostron/rhacm-docs

4. - [X] Mandatory for GA content:

• [X] Add steps, the diff, known issue, and/or other important
  conceptual information in the following space:

Linking doc to detailed places for where the places need to be changed in this google doc
https://docs.google.com/document/d/1OiP9vx7xMYkMPwTjSV5rofEgNAy__dW46Qrl2pFpuCs/edit?usp=sharing

• [X] *Add Required access level *(example, *Cluster
  Administrator*) for the user to complete the task:

Cluster Administrator

• [X] Add verification at the end of the task, how does the user
  verify success (a command to run or a result to see?)

User verifies success in two places
in the frontend, user will see a success message pop up after successfully assigning a role to a user or group
in the backend, multiclusterroleassignemnt CR is created and in the yaml the status.condition shows success

Example yaml in the Multiclusterroleassignment CR

status:
  appliedClusters:
    - local-cluster
  conditions:
    - lastTransitionTime: '2026-01-30T19:07:04Z'
      message: 1 out of 1 ClusterPermissions applied successfully
      observedGeneration: 3
      reason: Applied
      status: 'True'
      type: Applied
    - lastTransitionTime: '2026-01-30T10:39:05Z'
      message: 2 out of 2 role assignments ready
      observedGeneration: 3
      reason: AssignmentsReady
      status: 'True'
      type: Ready
  roleAssignments:
    - createdAt: '2026-01-30T10:38:36Z'
      message: Applied to 1 clusters
      name: 355d1566ee0424fd
      reason: SuccessfullyApplied
      status: Active
    - createdAt: '2026-01-30T10:39:05Z'
      message: Applied to 1 clusters
      name: b32ba4096cbb5912
      reason: SuccessfullyApplied
      status: Active
 

• [X] Add link to dev story here:

https://issues.redhat.com/browse/ACM-26301

5. - [ ] Mandatory for bugs: What is the diff? Clearly define what the
problem is, what the change is, and link to the current documentation. Only
use this for a documentation bug.