> For the complete documentation index, see [llms.txt](https://help.novacuraflow.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.novacuraflow.com/6.12/development/flow-studio/environment/roles.md).
# Roles
Roles is used to categorize users in different ways and could be used for different purposes in Flow.\
Roles can for example be used to describe an organisational structure or to reflect different types of access groups.
A User can be connected to one or many Roles. In order to structure the roles, many different Role Trees can be created.\
There are two types of inheritance methods for each Role Tree; Inherit Children and Inherit Parent.
Workflows and inboxes are added into menus, roles are connected to menus and users get roles, and by that users getting access to workflows and inboxes.
1. Select a role group from the list to view and edit the information or click on *Add* in the top-right corner of the roles list to add a new role group.
2. When a new role group is created, enter a Group id and a Group name.
3. If the Roles group should Inherit Children, check the check box (Inherit Parent is default).
4. Click on the + button to add a new Role, a new role named New role will appear, rename the role by double-click the new role.
5. It is possible to add levles of roles, add another level by marking the role and click the + button, a new roles named New role will appear, double-click to rename the roles.
{% hint style="info" %}
**Tips:** Delete a role by marking the role to delete and tap delete on the key board.
{% endhint %}
**Connect the role to one or more menus and users, read more about menus and users here:**
{% content-ref url="/pages/-LuPWlCqEHuEIYLf1qw0" %}
[Menu](/6.12/development/flow-studio/applications/menu.md)
{% endcontent-ref %}
{% content-ref url="/pages/-LucCtMtJ8mZrRqHFrtI" %}
[Users](/6.12/development/flow-studio/environment/users.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://help.novacuraflow.com/6.12/development/flow-studio/environment/roles.md?ask=&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.
