From 336c9fd5131be531dcfa53ad09349e088e30cdc2 Mon Sep 17 00:00:00 2001 From: Ieva Date: Fri, 10 Jun 2022 16:10:50 +0100 Subject: [PATCH] doc fix (#50624) --- .../access-control/plan-rbac-rollout-strategy.md | 7 +------ 1 file changed, 1 insertion(+), 6 deletions(-) diff --git a/docs/sources/enterprise/access-control/plan-rbac-rollout-strategy.md b/docs/sources/enterprise/access-control/plan-rbac-rollout-strategy.md index cfa180ec896..780f407539a 100644 --- a/docs/sources/enterprise/access-control/plan-rbac-rollout-strategy.md +++ b/docs/sources/enterprise/access-control/plan-rbac-rollout-strategy.md @@ -47,12 +47,7 @@ You can take advantage of your current authentication provider to manage user an For example: 1. Map SAML, LDAP, or Oauth roles to Grafana basic roles (viewer, editor, or admin). -2. Use the Grafana Enterprise team sync feature to synchronize teams from your SAML, LDAP, or Oauth provider to Grafana. - - - If a team does not exist in Grafana, team sync creates it. - - If a team exists in Grafana, team sync updates its membership. - - For more information about team sync, refer to [Team sync]({{< relref "../../setup-grafana/configure-security/configure-team-sync/" >}}). +2. Use the Grafana Enterprise team sync feature to synchronize teams from your SAML, LDAP, or Oauth provider to Grafana. For more information about team sync, refer to [Team sync]({{< relref "../../setup-grafana/configure-security/configure-team-sync/" >}}). 3. Within Grafana, assign RBAC permissions to users and teams.