You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@devlake.apache.org by GitBox <gi...@apache.org> on 2023/01/09 02:48:21 UTC

[GitHub] [incubator-devlake-website] Startrekzky commented on a diff in pull request #377: docs: add doc on how to manage dashboard access

Startrekzky commented on code in PR #377:
URL: https://github.com/apache/incubator-devlake-website/pull/377#discussion_r1064252194


##########
docs/UserManuals/Dashboards/AccessControl.md:
##########
@@ -0,0 +1,44 @@
+---
+title: "Dashboard Access Control"
+sidebar_position: 2
+description: >
+  Dashboard Access Control
+---
+
+
+# Dashboard Access Control
+
+This tutorial shows how to leverage Grafana's role-based access control (RBAC) to manage what dashboards a user has access to. If you're setting up a single DevLake instance to be shared by multiple teams in your organization, this tutorial can help you achieve data segregation between teams.
+
+## Example solution: one folder for each team
+
+One of the simplest solutions is to create one Grafana folder for each team and assign permissions to teams at the folder level. Below is a step-by-step walk through.
+
+1. Sign in as Grafana admin and create a new folder
+
+![create-new-folder](/img/Grafana/create-new-folder.png)
+
+2. Click "Permissions" tab and remove the default access of "Editor (Role)"" and "Viewer (Role)"

Review Comment:
   There's one more "



-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: commits-unsubscribe@devlake.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org