diff --git a/content/rancher/v2.5/en/admin-settings/rbac/global-permissions/_index.md b/content/rancher/v2.5/en/admin-settings/rbac/global-permissions/_index.md
index acb01dce836..c9b0b19803b 100644
--- a/content/rancher/v2.5/en/admin-settings/rbac/global-permissions/_index.md
+++ b/content/rancher/v2.5/en/admin-settings/rbac/global-permissions/_index.md
@@ -43,6 +43,20 @@ CATTLE_RESTRICTED_DEFAULT_ADMIN=true
 ```
 ### List of `restricted-admin` Permissions
 
+The permissions for the `restricted-admin` role differ based on the Rancher version.
+
+{{% tabs %}}
+{{% tab "v2.5.6" %}}
+
+The `restricted-admin` permissions are as follows:
+
+- Has full admin access to all downstream clusters managed by Rancher.
+- Can add other users and assign them to clusters outside of the local cluster.
+- Can create other restricted admins.
+
+{{% /tab %}}
+{{% tab "v2.5.0-v2.5.5" %}}
+
 The `restricted-admin` permissions are as follows:
 
 - Has full admin access to all downstream clusters managed by Rancher.
@@ -51,6 +65,9 @@ The `restricted-admin` permissions are as follows:
 - Can create other restricted admins.
 - Cannot grant any permissions in the local cluster they don't currently have. (This is how Kubernetes normally operates)
 
+{{% /tab %}}
+{{% /tabs %}}
+
 ### Upgrading from Rancher with a Hidden Local Cluster
 
 Prior to Rancher v2.5, it was possible to run the Rancher server using this flag to hide the local cluster: