docs/sources/administration/user-management/manage-dashboard-permissions/index.md
Dashboard and folder permissions enable you to grant a viewer the ability to edit and save dashboard changes, or limit an editor's permission to modify a dashboard.
For more information about dashboard permissions, refer to Dashboard permissions.
When you grant user permissions for folders, that setting applies to all dashboards and subfolders contained in the folder. Consider using this approach to assigning dashboard and folder permissions when you have users, service accounts or teams who require access to groups of related dashboards or folders.
To grant dashboard folder permissions:
When you grant folder permissions, that setting applies to all dashboards and subfolders in the folder. For a more granular approach to assigning permissions, you can also assign user permissions to individual dashboards.
For example, if a user with the viewer organization role requires editor (or admin) access to a dashboard, you can assign those elevated permissions on an individual basis.
{{< admonition type="note" >}} If you have assigned a user dashboard folder permissions, you cannot also assign the user permission to dashboards contained in the folder. {{< /admonition >}}
Grant dashboard permissions when you want to restrict or enhance dashboard access for users who do not have permissions defined in the associated folder.
To grant dashboard permissions:
Edit dashboard permissions when you are want to enhance or restrict a user's access to a dashboard. For more information about dashboard permissions, refer to Dashboard permissions.
To edit dashboard permissions:
Grafana applies the highest permission a given user has to access a resource like a dashboard, so if you want to prevent a user from accessing a folder or dashboard you need to consider the user's organization role, folder permissions, and dashboard permissions.
Refer to the following examples to understand how organization and dashboard permissions impact a user's access to dashboards.
In this example, user1 has the editor organization role.
Dashboard permissions settings:
viewResult: User1 has edit permissions because the user's organization role is Editor.
In this example, user1 has the viewer organization role and is a member of team1.
Dashboard permissions settings:
editadminResult: User1 has administrator permissions for the dashboard because user1 is a member of team1.
In this example, user1 has the viewer organization role.
Dashboard permissions settings:
admin, which is inherited from the permissions set in parent foldereditResult: You receive an error message that cannot override a higher permission with a lower permission in the same dashboard. User1 has administrator permissions.
In this example, user1 has the viewer organization role.
Folder permissions settings:
edit, which is inherited from the permissions set in grandparent folderResult: User1 has editor permissions for the folder because user1 has permissions on a folder that contains this folder.
Refer to Role-based access Control in Grafana Enterprise to understand how to use RBAC permissions to restrict access to dashboards, folders, administrative functions, and other resources.