From 7b8e5467bb5a08c95652d0a32fe922217f4f6ea4 Mon Sep 17 00:00:00 2001 From: a3exodus <118157982+a3exodus@users.noreply.github.com> Date: Thu, 20 Mar 2025 09:51:56 +0100 Subject: [PATCH] Docs: Fix Incorrect LBAC Data Source Reference (#102509) --- .../administration/data-source-management/teamlbac/_index.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/sources/administration/data-source-management/teamlbac/_index.md b/docs/sources/administration/data-source-management/teamlbac/_index.md index 4bf449af022..af7c8f180cb 100644 --- a/docs/sources/administration/data-source-management/teamlbac/_index.md +++ b/docs/sources/administration/data-source-management/teamlbac/_index.md @@ -50,7 +50,7 @@ This feature addresses two common challenges faced by Grafana users: LBAC for data sources lets Grafana Teams use the same dashboard with different access control rules. To set up LBAC for data sources for a Loki data source, refer to [Configure LBAC for Loki Data Source](https://grafana.com/docs/grafana//administration/data-source-management/teamlbac/configure-teamlbac-for-loki/). -To set up LBAC for data sources for a Loki data source, refer to [Configure LBAC for Prometheus Data Source](https://grafana.com/docs/grafana//administration/data-source-management/teamlbac/configure-teamlbac-for-prometheus/). +To set up LBAC for data sources for a Prometheus data source, refer to [Configure LBAC for Prometheus Data Source](https://grafana.com/docs/grafana//administration/data-source-management/teamlbac/configure-teamlbac-for-prometheus/). ## Logs and Metrics Filtering with LBAC