Custom RBAC Roles with Grafana Provisioning in Open-Source Grafana-11.1.1

Hi,
I am trying to create a custom RBAC using Grafana provisioning.

I’ve created custom_role.yaml and added it under provisioning/access-control,

#cutom_role.yaml
apiVersion: 2
roles:
-name: ‘custom:users:writer’
uid: customuserswriter1
description: ‘List, create, or update other users.’
version: 2
orgId: 1
global: true
permissions:
- action: ‘users:read’
scope: ‘global.users:
- action: ‘users:write’
scope: 'global.users:

- action: ‘users:create’

then started the Grafana server with

#run.sh
exec grafana server
–homepath=“$GF_PATHS_HOME”
–config=“$GF_PATHS_CONFIG”
–packaging=docker
“$@”
cfg:default.log.mode=“console”
cfg:default.paths.data=“$GF_PATHS_DATA”
cfg:default.paths.logs=“$GF_PATHS_LOGS”
cfg:default.paths.plugins=“$GF_PATHS_PLUGINS”
cfg:default.paths.provisioning=“$GF_PATHS_PROVISIONING”

However, I can’t find the custom role after starting Grafana in Administration > Users and access > Users > Organization users > Role. I only see Admin, Viewer, and Editor roles.

Has anyone else faced this issue before?
Any insights or recommendations would be greatly appreciated.

Are you sure that RBAC is available in the OSS version and in the 11.1.1 version?

I am currently uncertain whether RBAC is supported in OSS. This is why I have posted my question here, to seek clarification and gather more information.

Available in Grafana Enterprise and Grafana Cloud.

Use debug logs to check that.

Grafana can provide valuable information about certain issues through its own debug logs. These logs can help troubleshoot and identify the root cause of problems (especially if they are related to anything that can be configured via Grafana config file).

To enable debug logging edit the configuration file grafana.ini:

[log]
# Either "console", "file", "syslog". Default is console and file
# Use space to separate multiple modes, e.g. "console file"
mode = console file

# Either "debug", "info", "warn", "error", "critical", default is "info"
level = debug

Then restart grafana for the setting to go into effect.

Replicate the problem and check Grafana logs.