ec9c3230eb
* Update _index.md * Update _index.md * Create server-admin-manage-users.md * content updates * Update server-admin-manage-users.md * content update * testing single sourcing * Update server-admin-manage-users.md * deleted index, updated sharing command * Update server-admin-manage-users.md * added index files to folders * Update _index.md * added task lists * Update server-admin-manage-users.md * working on single sourcing tests * content updates * Update server-admin-manage-users.md * Update server-admin-manage-users.md * Update server-admin-manage-users.md * add server admin manage orgs file * Update _index.md * Update _index.md * Content updates * Update server-admin-manage-orgs.md * Update server-admin-manage-users.md * Delete menu.yaml * Update _index.md * Update server-admin-manage-users.md * deleted old files * Update _index.md * temporarily removed some files * Update server-admin-manage-users.md * Made two relref changes to this branch. * Merge branch 'master' into docs-update-manage-users * Update server-admin-manage-orgs.md * Update server-admin-manage-users.md * add snippets and content changes * Content updates * Update server-admin-manage-users.md * Update server-admin-manage-orgs.md * added folders * content updates * Update server-admin-manage-users.md * Update server-admin-manage-users.md * testing step format * updated and clarified titles of snippets * Update server-admin-manage-users.md * Update server-admin-manage-users.md * Update _index.md * Update _index.md * Update _index.md * Update _index.md * Update server-admin-manage-users.md * Update server-admin-manage-users.md * content edits * Update _index.md * Update _index.md * Update _index.md * deleted old files * Update _index.md * Update _index.md * Update change-your-password.md * Update _index.md * Update _index.md * Update _index.md * moved files * Added user account profile topic * Update _index.md * Update _index.md * minor edits * update shortcodes * minor updates * Delete view-server-user-list-list.md * testing and updating shortcodes * edited content for single sourcing * Update example.md * added new snippet * updated content * Update _index.md * Added links * Content updates * Update docs/sources/manage-users/_index.md Co-authored-by: achatterjee-grafana <70489351+achatterjee-grafana@users.noreply.github.com> * Update docs/sources/manage-users/_index.md Co-authored-by: achatterjee-grafana <70489351+achatterjee-grafana@users.noreply.github.com> * Update docs/sources/manage-users/_index.md Co-authored-by: achatterjee-grafana <70489351+achatterjee-grafana@users.noreply.github.com> * Update docs/sources/manage-users/_index.md Co-authored-by: achatterjee-grafana <70489351+achatterjee-grafana@users.noreply.github.com> * Update docs/sources/manage-users/_index.md Co-authored-by: achatterjee-grafana <70489351+achatterjee-grafana@users.noreply.github.com> * Update docs/sources/manage-users/_index.md Co-authored-by: achatterjee-grafana <70489351+achatterjee-grafana@users.noreply.github.com> * Update docs/sources/manage-users/_index.md Co-authored-by: Ursula Kallio <73951760+osg-grafana@users.noreply.github.com> * Update docs/sources/manage-users/_index.md Co-authored-by: Ursula Kallio <73951760+osg-grafana@users.noreply.github.com> * Update _index.md Co-authored-by: achatterjee-grafana <aparajita.chatterjee@grafana.com> Co-authored-by: Robby Milo <robbymilo@gmail.com> Co-authored-by: achatterjee-grafana <70489351+achatterjee-grafana@users.noreply.github.com> Co-authored-by: Ursula Kallio <73951760+osg-grafana@users.noreply.github.com>
52 lines
2.9 KiB
Markdown
52 lines
2.9 KiB
Markdown
+++
|
|
title = "Permissions"
|
|
description = "Permissions"
|
|
keywords = ["grafana", "configuration", "documentation", "admin", "users", "datasources", "permissions"]
|
|
aliases = ["/docs/grafana/latest/permissions/overview/"]
|
|
weight = 50
|
|
+++
|
|
|
|
# Permissions
|
|
|
|
What you can do in Grafana is defined by the _permissions_ associated with your user account.
|
|
|
|
There are three types of permissions:
|
|
- Permissions granted as a Grafana Server Admin
|
|
- Permissions associated with your role in an organization
|
|
- Permissions granted to a specific folder or dashboard
|
|
|
|
You can be granted permissions based on:
|
|
- Grafana Server Admin status.
|
|
- Organization role (Admin, Editor, or Viewer).
|
|
- Folder or dashboard permissions assigned to your team (Admin, Editor, or Viewer).
|
|
- Folder or dashboard permissions assigned to your user account (Admin, Editor, or Viewer).
|
|
- (Grafana Enterprise) Data source permissions. For more information, refer to [Data source permissions]({{< relref "../enterprise/datasource_permissions.md" >}}) in [Grafana Enterprise]({{< relref "../enterprise" >}}).
|
|
- (Grafana Cloud) Grafana Cloud has additional roles. For more information, refer to [Grafana Cloud roles and permissions](/docs/grafana-cloud/cloud-portal/cloud-roles/).
|
|
|
|
## Grafana Server Admin role
|
|
|
|
Grafana server administrators have the **Grafana Admin** flag enabled on their account. They can access the **Server Admin** menu and perform the following tasks:
|
|
|
|
- Manage users and permissions.
|
|
- Create, edit, and delete organizations.
|
|
- View server-wide settings that are set in the [Configuration]({{< relref "../administration/configuration.md" >}}) file.
|
|
- View Grafana server stats, including total users and active sessions.
|
|
- Upgrade the server to Grafana Enterprise.
|
|
|
|
> **Note:** This role does not exist in Grafana Cloud.
|
|
|
|
## Organization roles
|
|
|
|
Users can belong to one or more organizations. A user's organization membership is tied to a role that defines what the user is allowed to do in that organization. For more information, refer to [Organization roles]({{< relref "../permissions/organization_roles.md" >}}).
|
|
|
|
## Dashboard and folder permissions
|
|
|
|
Dashboard and folder permissions allow you to remove the default role based permissions for Editors and Viewers and assign permissions to specific users and teams. Learn more about [Dashboard and folder permissions]({{< relref "dashboard_folder_permissions.md" >}}).
|
|
|
|
## Data source permissions
|
|
|
|
Per default, a data source in an organization can be queried by any user in that organization. For example a user with `Viewer` role can still
|
|
issue any possible query to a data source, not just those queries that exist on dashboards he/she has access to.
|
|
|
|
Data source permissions allows you to change the default permissions for data sources and restrict query permissions to specific **Users** and **Teams**. For more information, refer to [Data source permissions]({{< relref "../enterprise/datasource_permissions.md" >}}) in [Grafana Enterprise]({{< relref "../enterprise" >}}).
|