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

**URL:** <https://community.grafana.com/t/custom-rbac-roles-with-grafana-provisioning-in-open-source-grafana-11-1-1/145124>\
**Category:** Grafana\
**Tags:** rbac\
**Created:** [February 27, 2025, 12:36pm UTC](https://community.grafana.com/t/custom-rbac-roles-with-grafana-provisioning-in-open-source-grafana-11-1-1/145124 "2025-02-27T12:36:51Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![tarek82mmm](https://avatars.discourse-cdn.com/v4/letter/t/f07891/32.png) [@tarek82mmm](https://community.grafana.com/u/tarek82mmm)\
**Post date:** [February 27, 2025, 12:36pm UTC](https://community.grafana.com/t/custom-rbac-roles-with-grafana-provisioning-in-open-source-grafana-11-1-1/145124/1 "2025-02-27T12:36:51Z")

</div>

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.

---

<div class="post-metadata">

**Author:** ![jangaraj](https://sea2.discourse-cdn.com/grafana/user_avatar/community.grafana.com/jangaraj/32/39197_2.png) [@jangaraj](https://community.grafana.com/u/jangaraj)\
**Post date:** [February 27, 2025, 1:18pm UTC](https://community.grafana.com/t/custom-rbac-roles-with-grafana-provisioning-in-open-source-grafana-11-1-1/145124/2 "2025-02-27T13:18:17Z")

</div>

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

---

<div class="post-metadata">

**Author:** ![tarek82mmm](https://avatars.discourse-cdn.com/v4/letter/t/f07891/32.png) [@tarek82mmm](https://community.grafana.com/u/tarek82mmm)\
**Post date:** [February 27, 2025, 2:51pm UTC](https://community.grafana.com/t/custom-rbac-roles-with-grafana-provisioning-in-open-source-grafana-11-1-1/145124/3 "2025-02-27T14:51:15Z")

</div>

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.

---

<div class="post-metadata">

**Author:** ![jangaraj](https://sea2.discourse-cdn.com/grafana/user_avatar/community.grafana.com/jangaraj/32/39197_2.png) [@jangaraj](https://community.grafana.com/u/jangaraj)\
**Post date:** [February 27, 2025, 3:53pm UTC](https://community.grafana.com/t/custom-rbac-roles-with-grafana-provisioning-in-open-source-grafana-11-1-1/145124/4 "2025-02-27T15:53:10Z")

</div>

> **[Grafana Role-based access control (RBAC) | Grafana documentation](https://grafana.com/docs/grafana/latest/administration/roles-and-permissions/access-control/)**
>
> Role-based access control (RBAC) provides a standardized way of granting, changing, and revoking access so that users can view and modify Grafana resources, such as users and reports.

> Available in [Grafana Enterprise](https://grafana.com/docs/grafana/latest/introduction/grafana-enterprise/) and [Grafana Cloud](https://grafana.com/docs/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](https://grafana.com/docs/grafana/latest/setup-grafana/configure-grafana/#configure-grafana) `grafana.ini`:

```auto
[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.