Important: This documentation is about an older version. It's relevant only to the release noted, many of the features and functions have been updated or replaced. Please view the current version.

Documentation Grafana documentation Permissions Restricting access

Restricting access

Refer to Fine-grained access Control in Grafana Enterprise to understand how to use fine-grained permissions to restrict access.

The highest permission always wins so if you for example want to hide a folder or dashboard from others you need to remove the Organization Role based permission from the Access Control List (ACL).

• You cannot override permissions for users with the Organization Admin role. Admins always have access to everything.
• A more specific permission with a lower permission level will not have any effect if a more general rule exists with higher permission level. You need to remove or lower the permission level of the more general rule.

Here are some examples of how Grafana resolves multiple permissions.

Example 1 (user1 has the Editor Role)

Permissions for a dashboard:

• Everyone with Editor role can edit
• user1 can view

Result: user1 has Edit permission as the highest permission always wins.

Example 2 (user1 has the Viewer Role and is a member of team1)

Permissions for a dashboard:

• Everyone with Viewer role can view
• user1 Can Edit
• team1 Can Admin

Result: user1 has Admin permission as the highest permission always wins.

Example 3

Permissions for a dashboard:

• user1 can admin (inherited from parent folder)
• user1 can edit

Result: You cannot override to a lower permission. user1 has Admin permission as the highest permission always wins.