diff --git a/plugins/rbac-backend/README.md b/plugins/rbac-backend/README.md
index c43a3d6147..574d88f1b6 100644
--- a/plugins/rbac-backend/README.md
+++ b/plugins/rbac-backend/README.md
@@ -10,7 +10,7 @@ With the RBAC plugin, you'll have the means to efficiently administer permission
Before you dive into utilizing the RBAC plugin for Backstage, there are a few essential prerequisites to ensure a seamless experience. Please review the following requirements to make sure your environment is properly set up
-### Setup Permision Framework
+### Setup Permission Framework
To effectively utilize the RBAC plugin, you must have the Backstage permission framework in place. If you're using the Red Hat Developer Hub, some of these steps may have already been completed for you. However, for other Backstage application instances, please verify that the following prerequisites are satisfied:
@@ -264,6 +264,8 @@ permission:
The maxDepth must be greater than 0 to ensure that the graphs are built correctly. Also the graph will be built with a hierarchy of 1 + maxDepth.
+More information about group hierarchy can be found in the doc: [Group hierarchy](./docs/group-hierarchy.md).
+
### Optional RBAC provider module support
We also include the ability to create and load in RBAC backend plugin modules that can be used to make connections to third part access management tools. For more information, consult the [RBAC Providers documentation](./docs/providers.md).
diff --git a/plugins/rbac-backend/docs/group-hierarchy.md b/plugins/rbac-backend/docs/group-hierarchy.md
new file mode 100644
index 0000000000..e2bab1998a
--- /dev/null
+++ b/plugins/rbac-backend/docs/group-hierarchy.md
@@ -0,0 +1,234 @@
+# Group Hierarchy
+
+RBAC access control is configured by defining roles and their associated permission policies, which
+are then assigned to users or groups. Leveraging group hierarchy can greatly simplify RBAC management,
+making it more scalable and flexible.
+
+## Group-Based Role Assignment
+
+Role can be assigned to a specific group. If a user is a member of that group, or a member of any of
+its child groups, the role (and its associated permissions) will automatically be applied to that user.
+
+Examples:
+
+- Sam will inherit `role:default/test` from `team-group` via `subteam-group`.
+
+ 
+
+ ```yaml
+ # catalog-entity.yaml
+ apiVersion: backstage.io/v1alpha1
+ kind: Group
+ metadata:
+ name: team-group
+ spec:
+ type: team
+ children: [subteam-group]
+ ---
+ apiVersion: backstage.io/v1alpha1
+ kind: Group
+ metadata:
+ name: subteam-group
+ spec:
+ type: team
+ children: []
+ parent: team-group
+ ---
+ apiVersion: backstage.io/v1alpha1
+ kind: User
+ metadata:
+ name: sam
+ spec:
+ memberOf:
+ - subteam-group
+ ```
+
+ ```CSV
+ g, group:default/team-group, role:default/test
+ p, role:default/test, catalog-entity, read, allow
+ ```
+
+- Sam will have `role:default/test` via `team-group`.
+
+ 
+
+ ```yaml
+ # catalog-entity.yaml
+ apiVersion: backstage.io/v1alpha1
+ kind: User
+ metadata:
+ name: sam
+ ---
+ apiVersion: backstage.io/v1alpha1
+ kind: Group
+ metadata:
+ name: team-group
+ spec:
+ type: team
+ children: []
+ members:
+ - sam
+ ```
+
+ ```CSV
+ g, group:default/team-group, role:default/test
+ p, role:default/test, catalog-entity, read, allow
+ ```
+
+- Sam will inherit `role:default/role-a` from `group-a` and `role:default/role-c` from `group-c`.
+
+ 
+
+ ```yaml
+ # catalog-entity.yaml
+ apiVersion: backstage.io/v1alpha1
+ kind: Group
+ metadata:
+ name: group-a
+ spec:
+ type: team
+ children: [group-b]
+ ---
+ apiVersion: backstage.io/v1alpha1
+ kind: Group
+ metadata:
+ name: group-b
+ spec:
+ type: team
+ children: []
+ ---
+ apiVersion: backstage.io/v1alpha1
+ kind: Group
+ metadata:
+ name: group-c
+ spec:
+ type: team
+ children: []
+ ---
+ apiVersion: backstage.io/v1alpha1
+ kind: User
+ metadata:
+ name: sam
+ spec:
+ memberOf:
+ - group-b
+ - group-c
+ ```
+
+ ```CSV
+ g, group:default/group-a, role:default/role-a
+ g, group:default/group-c, role:default/role-c
+ p, role:default/role-a, catalog-entity, read, allow
+ p, role:default/role-c, catalog-entity, delete, allow
+ ```
+
+## Managing Group Hierarchy Depth
+
+While group hierarchy provides powerful inheritance features, it can have performance implications.
+Organizations with potentially complex group hierarchy can specify `maxDepth` configuration value,
+that will ensure that the RBAC plugin will stop at a certain depth when building user graphs.
+
+```YAML
+permission:
+ enabled: true
+ rbac:
+ maxDepth: 1
+```
+
+The `maxDepth` must be greater than 0 to ensure that the graphs are built correctly. Also the graph
+will be built with a hierarchy of 1 + maxDepth.
+
+## Non-Existent Groups in the Hierarchy
+
+For group hierarchy to function, groups don't need to be present in the catalog as long as the group
+has an existing parent group or is a member of existing group or an existing user is a member of
+that group.
+(Note that this does not work with in-memory database.)
+
+Examples:
+
+- Sam will inherit `role:default/test`, although `team-group` isn't explicitly defined.
+
+ 
+
+ ```yaml
+ # catalog-entity.yaml
+ apiVersion: backstage.io/v1alpha1
+ kind: User
+ metadata:
+ name: sam
+ spec:
+ memberOf:
+ - team-group
+ ```
+
+ ```CSV
+ g, group:default/team-group, role:default/test
+ p, role:default/test, catalog-entity, read, allow
+ ```
+
+- Sam will inherit `role:default/test` via `subteam-group` that is a child of `team-group`, although `subteam-group` isn't explicitly defined.
+
+ 
+
+ ```yaml
+ # catalog-entity.yaml
+ apiVersion: backstage.io/v1alpha1
+ kind: User
+ metadata:
+ name: sam
+ spec:
+ memberOf:
+ - subteam-group
+ ---
+ apiVersion: backstage.io/v1alpha1
+ kind: Group
+ metadata:
+ name: team-group
+ spec:
+ type: team
+ children: [subteam-group]
+ ```
+
+ ```CSV
+ g, group:default/team-group, role:default/test
+ p, role:default/test, catalog-entity, read, allow
+ ```
+
+- Sam will inherit `role:default/test` via `group-d` <- `group-c` <- `group-b` <- `group-a`,
+ although `group-d` and `group-b` aren't explicitly defined.
+
+ 
+
+ ```yaml
+ # catalog-entity.yaml
+ apiVersion: backstage.io/v1alpha1
+ kind: User
+ metadata:
+ name: sam
+ spec:
+ memberOf:
+ - group-d
+ ---
+ apiVersion: backstage.io/v1alpha1
+ kind: Group
+ metadata:
+ name: group-c
+ spec:
+ type: team
+ children: [group-d]
+ parent: group-b
+ ---
+ apiVersion: backstage.io/v1alpha1
+ kind: Group
+ metadata:
+ name: group-a
+ spec:
+ type: team
+ children: [group-b]
+ ```
+
+ ```CSV
+ g, group:default/group-a, role:default/test
+ p, role:default/test, catalog-entity, read, allow
+ ```
diff --git a/plugins/rbac-backend/docs/images/group-hierarchy-1.svg b/plugins/rbac-backend/docs/images/group-hierarchy-1.svg
new file mode 100644
index 0000000000..573bb26c68
--- /dev/null
+++ b/plugins/rbac-backend/docs/images/group-hierarchy-1.svg
@@ -0,0 +1 @@
+
\ No newline at end of file
diff --git a/plugins/rbac-backend/docs/images/group-hierarchy-2.svg b/plugins/rbac-backend/docs/images/group-hierarchy-2.svg
new file mode 100644
index 0000000000..86156c7fcd
--- /dev/null
+++ b/plugins/rbac-backend/docs/images/group-hierarchy-2.svg
@@ -0,0 +1 @@
+
\ No newline at end of file
diff --git a/plugins/rbac-backend/docs/images/group-hierarchy-3.svg b/plugins/rbac-backend/docs/images/group-hierarchy-3.svg
new file mode 100644
index 0000000000..62f819f0d0
--- /dev/null
+++ b/plugins/rbac-backend/docs/images/group-hierarchy-3.svg
@@ -0,0 +1 @@
+
\ No newline at end of file
diff --git a/plugins/rbac-backend/docs/images/group-hierarchy-4.svg b/plugins/rbac-backend/docs/images/group-hierarchy-4.svg
new file mode 100644
index 0000000000..3fd7d85ee8
--- /dev/null
+++ b/plugins/rbac-backend/docs/images/group-hierarchy-4.svg
@@ -0,0 +1 @@
+