Documentation for automated readers
A curated documentation index is available at: https://grafana.com/llms.txt
A complete documentation index is available at: https://grafana.com/llms-full.txt
These indexes can help with page discovery before fetching individual documents.
This page is also available in Markdown, which may be easier for automated readers and AI tools to parse than HTML. The Markdown version is available at https://grafana.com/docs/grafana-cloud/platform/security-and-account-management/security-and-access/authentication-and-permissions/plan-access-management.md, or by sending Accept: text/markdown to https://grafana.com/docs/grafana-cloud/platform/security-and-account-management/security-and-access/authentication-and-permissions/plan-access-management/. For broader documentation discovery, the curated index is available at https://grafana.com/llms.txt and the complete index is available at https://grafana.com/llms-full.txt.
Plan access management for Grafana Cloud
Access control inside a Grafana stack is comprised of five building blocks, read left to right. Each one answers a single question.
| SSO | Teams | RBAC | Folders | LBAC | |
|---|---|---|---|---|---|
| Answers | Who are you? | Who are you with? | What can you do? | Which content can you affect? | What data can you query? |
Around those blocks, Grafana Cloud adds two more layers; the Cloud Portal, which manages your organization above every stack, and the telemetry data itself. Each layer has its own identity source, its own way of authorizing people, and its own way of authorizing machines. Most access management questions come down to working out which block or layer you need to change.
Several features also share names across layers.
Admin, Editor, and Viewer mean one thing in the Cloud Portal and something different inside a stack, and two separate features are both called label based access control (LBAC).
This section explains those distinctions and points you to the page that configures each control.
The three layers
| Layer | Who signs in | Authorization for people | Authorization for machines |
|---|---|---|---|
| Cloud Portal | Grafana.com accounts, using basic authentication, social login, or SAML, which is in private preview | Cloud Portal roles, which cover billing, stacks, organization members, and access policies | Access policy tokens |
| Stack | The Cloud Portal by default, or an identity provider you connect to the stack with SAML, OAuth, OIDC, or LDAP | Basic roles, teams, role-based access control (RBAC), folder and dashboard permissions, data source permissions | Service account tokens |
| Data | Nobody signs in to this layer. You reach it through a stack data source or directly through the HTTP API | LBAC for data sources, which filters query results by a user’s team memberships | Access policy label selectors, which filter query results by token |
Find the page you need
| What you want to do | Feature to use | Where to go |
|---|---|---|
| Let people sign in to a stack with your company identity provider | Stack authentication | Configure authentication |
| Control who can manage billing, stacks, and organization members | Cloud Portal roles | Grafana Cloud user roles and permissions |
| Control what a person can do inside a Grafana stack | RBAC | Role-based access control (RBAC) |
| Decide which dashboards and folders each team can edit | Folder permissions | Manage dashboard permissions |
| Let a script manage dashboards, users, or alerts | Service account and token | Service accounts |
| Send or query telemetry from outside Grafana | Access policy and token | Grafana Cloud Access Policies |
| Restrict which metrics or logs a token can read | LBAC with access policies | Use label-based access control (LBAC) with access policies |
| Restrict which data each team sees in a shared data source | LBAC for data sources | Label-based access control (LBAC) for data sources |
| Control access to a Grafana Cloud app, such as IRM, SLO, or k6 | Plugin RBAC roles, or the app’s own roles | Grafana Cloud app plugin role definitions |
| Create users and teams automatically from your identity provider | SCIM provisioning or team sync | Configure SCIM provisioning |
| Require a second factor when people sign in to the Cloud Portal | Multi-factor authentication | Set up multi-factor authentication (MFA) |
In this section
- How Grafana Cloud access controls work together explains the five building blocks and the three layers in detail, tells apart the features that overlap, and describes the order in which Grafana evaluates them.
Related documentation
- Configure authentication and authorization describes the Cloud Portal and stack authentication layers.
- Stack architecture recommendations covers when to use one stack and when to use several.
- Plan your IAM integration strategy is the equivalent planning guide for self-managed Grafana.
Was this page helpful?
Related resources from Grafana Labs


