From 010fd4240fc3f78a8c54d45c380dba36b016dfbd Mon Sep 17 00:00:00 2001
From: xavi <114113189+volcanonoodle@users.noreply.github.com>
Date: Tue, 10 Jun 2025 12:17:05 +0200
Subject: [PATCH] [IAM] Docs: Add permission behaviour when user belongs to
 multiple teams (#106429)

---
 docs/sources/administration/team-management/_index.md | 2 ++
 1 file changed, 2 insertions(+)

diff --git a/docs/sources/administration/team-management/_index.md b/docs/sources/administration/team-management/_index.md
index e83e83ab62c..0a35b764cb7 100644
--- a/docs/sources/administration/team-management/_index.md
+++ b/docs/sources/administration/team-management/_index.md
@@ -42,6 +42,8 @@ A Team grants permissions to a wide variety of resources including:
 
 {{< admonition type="note" >}}
 All members of a Grafana Team have the same exact permissions. A single Team can't have members with different access levels to resources shared within that Team.
+
+Additionally, when a user belongs to multiple Teams that have different permission levels for the same resource, the user receives the highest (most permissive) access level from any of their Teams. For example, if a user belongs to two Teams, one with Viewer access and another with Editor access to a folder, the user will have Editor access to that folder.
 {{< /admonition >}}
 
 A user can be a `Member` or an `Administrator` for a given Team. `Members` of a Team inherit permissions from the team, but they don't have team administrator privileges, and can't edit the team itself. Team `Administrators` can add members to a team and update its settings, such as the team name, team member’s team roles, UI preferences, and home dashboard.