[v11.2.x] LBAC for datasources: doc improvements (#92918)

Co-authored-by: Jack Baldry <jack.baldry@grafana.com>
Co-authored-by: Eric Leijonmarck <eric.leijonmarck@gmail.com>

docs/sources/administration/data-source-management/teamlbac/_index.md

@@ -19,6 +19,10 @@ Team Label Based Access Control (LBAC) simplifies and streamlines data source ac
 {{< admonition type="note" >}}
 Creating Team LBAC rules is available for preview for logs with Loki in Grafana Cloud.
 Report any unexpected behavior to the Grafana Support team.
+
+To use Team LBAC rules you must enable the `teamHttpHeaders` feature toggle because the feature uses HTTP headers for the LBAC rules requests.
+
+- Be sure that you are running Grafana Enterprise.
   {{< /admonition >}}
 
 You can configure user access based upon team memberships using LogQL.

docs/sources/administration/data-source-management/teamlbac/configure-teamlbac-for-loki/index.md

@@ -19,6 +19,7 @@ Team LBAC is available in private preview on Grafana Cloud for Loki created with
 
 To be able to use Team LBAC rules, you need to enable the feature toggle `teamHttpHeaders` on your Grafana instance. Contact support to enable the feature toggle for you.
 
+- Be sure that you are running Grafana Enterprise.
 - Be sure that you have the permission setup to create a loki tenant in Grafana Cloud
 - Be sure that you have admin data source permissions for Grafana.
 

docs/sources/administration/data-source-management/teamlbac/create-teamlbac-rules/index.md

@@ -18,6 +18,9 @@ Team LBAC is available on Cloud for data sources created with basic authenticati
 
 ## Before you begin
 
+To be able to use Team LBAC rules, you need to enable the feature toggle `teamHttpHeaders` on your Grafana instance. Contact support to enable the feature toggle for you.
+
+- Be sure that you are running Grafana Enterprise.
 - Be sure that you have admin data source permissions for Grafana.
 - Be sure that you have a team setup in Grafana.