A role represents set of permissions that allow you to perform specific actions on Grafana resources. Refer to Permissions to understand how permissions work.
There are two types of roles:
- Fixed roles, which provide granular access for specific resources within Grafana and are managed by the Grafana itself.
- Custom roles, which provide granular access based on the user specified set of permissions.
You can use Fine-grained access control API to list available roles and permissions.
A role can be either global or organization local. Global roles are not mapped to any specific organization and can be reused across multiple organizations, whereas organization local roles are only available for that specific organization.
Fixed roles provide convenience and guarantee of consistent behaviour by combining relevant permissions together. Fixed roles are created and updated by Grafana during startup. There are few basic rules for fixed roles:
- All fixed roles are global.
- All fixed roles have a
- You can’t change or delete a fixed role.
For more information, refer to Fine-grained access control references.
A role’s name is intended as a human friendly identifier for the role, helping administrators understand the purpose of a role. The name cannot be longer than 190 characters, and we recommend using ASCII characters. Role names must be unique within an organization.
Roles with names prefixed by
fixed: are fixed roles created by Grafana and cannot be created or modified by users.
A role’s display name is intended as a human friendly identifier for the role, helping users understand the purpose of a role. The display name of the role is displayed in the role picker in the UI.
A role’s group is used to organize roles in the role picker in the UI.
The version of a role is a positive integer which defines the current version of the role. When updating a role, you can either omit the version field to increment the previous value by 1 or set a new version which must be strictly larger than the previous version for the update to succeed.
You manage access to Grafana resources by mapping permissions to roles. You can create and assign roles without any permissions as placeholders.
Each custom role has a UID defined which is a unique identifier associated with the role allowing you to change or delete the role. You can either generate UID yourself, or let Grafana generate one for you.
The same UID cannot be used for roles in different organizations within the same Grafana instance.
Create, update and delete roles
By default, Grafana Server Admin has a built-in role assignment which allows a user to create, update or delete custom roles.
If a Grafana Server Admin wants to delegate that privilege to other users, they can create a custom role with relevant permissions and
permissions:delegate scope will allow those users to manage roles themselves.
Note that you won’t be able to create, update or delete a custom role with permissions which you yourself do not have. For example, if the only permission you have is a
users:create, you won’t be able to create a role with other permissions.
Visit Manage role assignments page for more details.
Scope of assignments
A role assignment can be either global or organization local. Global assignments are not mapped to any specific organization and will be applied to all organizations, whereas organization local assignments are only applied for that specific organization. You can only create organization local assignments for organization local roles.
Related Grafana resources
Unify your data with Grafana plugins: Splunk, MongoDB, Datadog, and more
Show how Grafana can be used to take data from multiple different sources and unify it, without disrupting the investments that are working today.
Getting started with Grafana Enterprise and observability
Join the Grafana Labs team for a 30-minute demo of how to get started with the Grafana Stack, so you can go from zero to observability in just a few minutes.