From b40f192c7ea7e22d0f66045f0937b056d62a8230 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Giuseppe=20Crin=C3=B2?= Date: Mon, 7 Nov 2022 11:39:59 +0100 Subject: [PATCH] chore(docs): clarify how to refer to GH teams (#57679) --- .../configure-security/configure-authentication/github/index.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/sources/setup-grafana/configure-security/configure-authentication/github/index.md b/docs/sources/setup-grafana/configure-security/configure-authentication/github/index.md index f82fb1a08c4..1f8c90fb14e 100644 --- a/docs/sources/setup-grafana/configure-security/configure-authentication/github/index.md +++ b/docs/sources/setup-grafana/configure-security/configure-authentication/github/index.md @@ -143,7 +143,7 @@ if you have a team called 'example-group' you can use the following snippet to ensure those members inherit the role 'Editor'. ```bash -role_attribute_path = contains(groups[*], '@github/example-group') && 'Editor' || 'Viewer' +role_attribute_path = contains(groups[*], '@my-github-organization/my-github-team') && 'Editor' || 'Viewer' ``` Note: If a match is found in other fields, teams will be ignored.