> For the complete documentation index, see [llms.txt](https://docs.qubitro.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.qubitro.com/platform/monitoring/dashboards/roles-and-permission.md).

# Roles & Permission

Define and manage user roles to control access to dashboards.

The Roles & Permissions tab defines how collaborators interact with dashboard content. This includes permissions to view, edit, delete, and manage dashboard access.

{% hint style="info" %}
A resource in this context refers to a dashboard—its layout, widgets, settings, and access controls.
{% endhint %}

Qubitro provides three default roles—**Read-Only**, **Read/Write**, and **Admin**—each granting a different level of access.

{% hint style="success" %}
If your plan or organization settings allow for custom roles, you can define additional role types with more granular permissions.
{% endhint %}

### Default Roles

#### Read-Only

Users can view dashboards but cannot make any changes.

{% hint style="info" %}
**Examples:**

* Can view the dashboard in View mode
* Cannot switch to Edit mode or update widgets
* Cannot access settings or sharing options
  {% endhint %}

#### Read/Write

Users can modify the dashboard layout and widgets, but cannot delete the dashboard or manage access.

{% hint style="info" %}
**Examples:**

* Can switch to Edit mode and configure widgets
* Can change layout and refresh settings
* Cannot delete the dashboard or invite collaborators
  {% endhint %}

#### Admin

Users have full access to manage the dashboard, including editing, deleting, and managing collaborators.

{% hint style="info" %}
**Examples:**

* Can delete the dashboard
* Can invite or remove collaborators and change roles
* Can update all general and configuration settings
  {% endhint %}

### Roles Reference

| Action              | Read-Only | Read/Write | Admin |
| ------------------- | --------- | ---------- | ----- |
| View Dashboard      | ✅         | ✅          | ✅     |
| Edit Layout/Widgets | ❌         | ✅          | ✅     |
| Change Settings     | ❌         | ✅          | ✅     |
| Delete Dashboard    | ❌         | ❌          | ✅     |
| Access Management   | ❌         | ❌          | ✅     |

### Custom Roles

Custom roles allow Organizations to define more granular access controls beyond the default roles. You can specify exactly which actions are allowed—such as editing widgets but not layout, or enabling refresh without access to sharing options.

{% hint style="warning" %}
Custom roles are available only for **Organizations** and must be created in the **Organization Settings**.
{% endhint %}

Once created, custom roles can be assigned to collaborators from the **Access Management** tab of any dashboard.

{% content-ref url="/pages/ivg9wjLtoHiB3qIaDoI7" %}
[Custom Roles](/organizations/custom-roles.md)
{% endcontent-ref %}


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.qubitro.com/platform/monitoring/dashboards/roles-and-permission.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.