public/grafana
1
0 Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

doc fix (#50624) (#50626)

Browse Source 
(cherry picked from commit 336c9fd513)

Co-authored-by: Ieva <ieva.vasiljeva@grafana.com>
This commit is contained in:
Grot (@grafanabot)andIeva authored and GitHub committed 2022-06-10 17:17:40 +02:00
1 parent 5d9178f6ab
commit fa4fa0bf4f
1 file changed
+1 -6
Download Patch File Download Diff File Expand all files Collapse all files
docs/sources/enterprise/access-control/plan-rbac-rollout-strategy.md
+1 -6
View File
@@ -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.