> For the complete documentation index, see [llms.txt](https://docs.hackle.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.hackle.io/en/workspace/roles.md).

# Permission Management

{% hint style="info" %}
This feature is only available on the Enterprise plan.
{% endhint %}

### Overview

This feature allows you to manage Dashboard users' access and usage permissions on a per-menu basis in detail.

You can create Custom permissions so that only specific users can control A/B Tests and Feature Flags, while the remaining users can only create data analytics charts and are restricted to read-only access for A/B Tests and Feature Flags.

Data viewing and download permissions can also be controlled per menu for purposes such as personal data management.

### Creating and Configuring Permissions

Assigning created permissions to Dashboard users is done from the 'Workspace Settings' menu. Click the gear icon at the top of the Dashboard to access the 'Workspace Settings' menu.

![](/files/46zgwO1MakBd6i6sfaVW)

Creating and managing Custom permissions is done from the 'Permission Management' menu. Go to Workspace Settings > Permission Management. Click the **'+ Create Permission'** button to create a Custom permission.

![](/files/JZr2YONBNikDS8EZft8i)

Permissions can be assigned at the menu level as provided in the Dashboard. For each menu, you can assign edit (write), read-only (read), data download (raw data download), and data read (view data collection status) permissions separately.

To assign a specific permission across all menus, turn on the corresponding permission toggle among the 4 toggle buttons in the permission configuration section, such as 'All Edit Permissions'.

![](/files/43FXiYxRWLASesOi6jCE)


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.hackle.io/en/workspace/roles.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.