Changes for page Grafana

Summary

• Page properties (1 modified, 0 added, 0 removed)

Details

Page properties

Content

...	...	@@ -42,17 +42,18 @@
42	42	Projects in DevOps portal are mapped to Grafana Organizations. These are not related to the organizations in the portal.
43	43	)))
44	44
45		-* When there is a new project in the portal having Grafana as a configured tool, then there is a new Grafana "Org". Users assigned to a project in the portal are then assigned to a Grafana Org applying the configured roles.
	45	+* When there is a new project in the portal having Grafana as a configured tool, then there is a new Grafana Organization. Users assigned to a project in the portal are then assigned to a Grafana Organization applying the configured roles.
46	46	** Role mapping: (((
47		-|=Project Role in DevOps Portal|=Grafana Organization Role|=Permissions in Grafana
48		-|Viewer|Viewer|Can view dashboards and alerts
49		-|Developer / Master|Editor|Can create/edit dashboards and alerts and use the Explore function
	47	+(% class="active" %)|=Project Role in DevOps Portal|=Grafana Organization Role|=Permissions in Grafana
50	50	|Admin|Admin|Has full permissions within the Grafana org, e.g. can setup datasources, manage folders, teams and service accounts
	49	+|Master|(% colspan="1" rowspan="2" %)Editor|(% colspan="1" rowspan="2" %)Can create/edit dashboards and alerts and use the Explore function
	50	+|Developer
	51	+|Viewer|Viewer|Can view dashboards and alerts
51	51
52	52	A detailed description of the Grafana role model can be found [[here>>https://grafana.com/docs/grafana/latest/administration/roles-and-permissions/]].
53	53	)))
54	54	* There is an additional permission management possible on folder level. A folder contains a set of dashboards. A project admin can create folders and manage specific permissions for this folder using Grafana. See this [[link >>https://grafana.com/docs/grafana/latest/dashboards/manage-dashboards/#create-a-dashboard-folder]]for further information. Folder permissions management is out of scope of the user management in the DevOps portal.
55		-* A project admin is entitled to create and manage "Service Accounts" in Grafana and grant permissions in the specific organization. A Service Account belongs to an Organization (Project) and not to an user. Service Accounts can be used for systems which want to work wit the Grafana API for any automation purposes. See this [[link >>https://grafana.com/docs/grafana/latest/administration/service-accounts/]]for further information. Service Account management is done directly in Grafana and is out of scope of the user management in the DevOps portal.
	56	+* A project admin is entitled to create and manage "Service Accounts" in Grafana and grant permissions in the specific organization. A Service Account belongs to an Organization and not to an user. Service Accounts can be used for systems which want to work wit the Grafana API for any automation purposes. See this [[link >>https://grafana.com/docs/grafana/latest/administration/service-accounts/]]for further information. Service Account management is done directly in Grafana and is out of scope of the user management in the DevOps portal. This function is comparable with the Technical Users feature in the DevOps portal.
56	56	* If you are assigned to more than one project in the DevOps portal, having Grafana configured as tool, then you can switch between Organizations in Grafana. Go to the top left corner, click on the Org list and select any other Grafana Organization (project), you want to switch to.
57	57	[[image:1744272203893-682.png||height="272" width="255"]]
58	58