Docs: Make role definitions more precise (#102391)

* fix missing clarification

* remove OnCall admonitions
This commit is contained in:
Jo
2025-03-20 16:12:29 +01:00
committed by GitHub
parent 58eabf8ad6
commit 7411472f52
@@ -50,7 +50,7 @@ refs:
Available in [Grafana Enterprise](/docs/grafana/<GRAFANA_VERSION>/introduction/grafana-enterprise/) and [Grafana Cloud](/docs/grafana-cloud).
{{% /admonition %}}
The following tables list permissions associated with basic and fixed roles.
The following tables list permissions associated with basic and fixed roles. This does not include basic role assignments added by plugins or apps.
## Basic role assignments
@@ -165,16 +165,7 @@ There is only one exclusion at this moment. Role `fixed:alerting.provisioning:wr
For more information about the permissions required to access alert rules, refer to [Create a custom role to access alerts in a folder](ref:plan-rbac-rollout-strategy-create-a-custom-role-to-access-alerts-in-a-folder).
### Grafana OnCall roles (beta)
{{% admonition type="note" %}}
Available from Grafana 9.4 in early access.
{{% /admonition %}}
{{% admonition type="note" %}}
This feature is behind the `accessControlOnCall` feature toggle.
You can enable feature toggles through configuration file or environment variables. See configuration [docs](/docs/grafana/<GRAFANA_VERSION>/setup-grafana/configure-grafana/#feature_toggles) for details.
{{% /admonition %}}
### Grafana OnCall roles
If you are using [Grafana OnCall](ref:oncall), you can try out the integration between Grafana OnCall and RBAC.
For a detailed list of the available OnCall RBAC roles, refer to the table in [Available Grafana OnCall RBAC roles and granted actions](ref:available-grafana-oncall-rbac-roles--granted-actions).