diff --git a/openmetadata-docs/content/v1.7.x/how-to-guides/admin-guide/teams-and-users/team-structure-openmetadata.md b/openmetadata-docs/content/v1.7.x/how-to-guides/admin-guide/teams-and-users/team-structure-openmetadata.md
index f08603aefaf..6758655399a 100644
--- a/openmetadata-docs/content/v1.7.x/how-to-guides/admin-guide/teams-and-users/team-structure-openmetadata.md
+++ b/openmetadata-docs/content/v1.7.x/how-to-guides/admin-guide/teams-and-users/team-structure-openmetadata.md
@@ -23,6 +23,12 @@ OpenMetadata supports a hierarchical team structure with **teamType** that can b
 {% /note noteType="Warning" %}
 {% /note %}
 
+{% note %}
+
+OpenMetadata supports flexible nested team hierarchies under organizational structures such as Business Unit, Division, and Department. While there is no hardcoded limit to the depth of hierarchy, leaf nodes such as "Group" cannot have child teams. Additionally, certain team types like "Department" cannot be nested within "Group." To extend the hierarchy, consider using other team types where appropriate.
+
+{% /note %}
+
 {% image
 src="/images/v1.7/how-to-guides/teams-and-users/teams.png"
 alt="team-structure"
diff --git a/openmetadata-docs/content/v1.8.x/how-to-guides/admin-guide/teams-and-users/team-structure-openmetadata.md b/openmetadata-docs/content/v1.8.x/how-to-guides/admin-guide/teams-and-users/team-structure-openmetadata.md
index bca525a2ad9..c73ec82575d 100644
--- a/openmetadata-docs/content/v1.8.x/how-to-guides/admin-guide/teams-and-users/team-structure-openmetadata.md
+++ b/openmetadata-docs/content/v1.8.x/how-to-guides/admin-guide/teams-and-users/team-structure-openmetadata.md
@@ -23,6 +23,12 @@ OpenMetadata supports a hierarchical team structure with **teamType** that can b
 {% /note noteType="Warning" %}
 {% /note %}
 
+{% note %}
+
+OpenMetadata supports flexible nested team hierarchies under organizational structures such as Business Unit, Division, and Department. While there is no hardcoded limit to the depth of hierarchy, leaf nodes such as "Group" cannot have child teams. Additionally, certain team types like "Department" cannot be nested within "Group." To extend the hierarchy, consider using other team types where appropriate.
+
+{% /note %}
+
 {% image
 src="/images/v1.8/how-to-guides/teams-and-users/teams.png"
 alt="team-structure"
diff --git a/openmetadata-docs/content/v1.9.x-SNAPSHOT/how-to-guides/admin-guide/teams-and-users/team-structure-openmetadata.md b/openmetadata-docs/content/v1.9.x-SNAPSHOT/how-to-guides/admin-guide/teams-and-users/team-structure-openmetadata.md
index 327e6ead986..8b63b683c6b 100644
--- a/openmetadata-docs/content/v1.9.x-SNAPSHOT/how-to-guides/admin-guide/teams-and-users/team-structure-openmetadata.md
+++ b/openmetadata-docs/content/v1.9.x-SNAPSHOT/how-to-guides/admin-guide/teams-and-users/team-structure-openmetadata.md
@@ -23,6 +23,12 @@ OpenMetadata supports a hierarchical team structure with **teamType** that can b
 {% /note noteType="Warning" %}
 {% /note %}
 
+{% note %}
+
+OpenMetadata supports flexible nested team hierarchies under organizational structures such as Business Unit, Division, and Department. While there is no hardcoded limit to the depth of hierarchy, leaf nodes such as "Group" cannot have child teams. Additionally, certain team types like "Department" cannot be nested within "Group." To extend the hierarchy, consider using other team types where appropriate.
+
+{% /note %}
+
 {% image
 src="/images/v1.9/how-to-guides/teams-and-users/teams.png"
 alt="team-structure"