> For the complete documentation index, see [llms.txt](https://docs.struct.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.struct.com/tutorials/guides/how-to-work-with-user-management/how-to-set-up-a-role.md).
# How to set up a role
## Setting up a role
On the 'User Management'-tab swap to the 'Roles'-page in the leftside navigation bar.
On the 'Roles'-page, click '+ Create role' to create a new role or click one of the existing roles to edit that role.
'Roles'-page
In this tutorial we will create a new role, but the process of creating a new role and editing an existing role is the same. Clicking '+Create role' presents you with the 'Create role'-page.
'Create role'-page
The first thing to do is to give the role a name. This name should reflect what the role can do, e.g. 'Editor', 'Translator' og 'Read only'. Next is adding the permissions.
The permissions are split into permission groups and clicking a permission group will reveal all permissions in that user group. Alternatively clicking 'Open all' will reveal all permissions.
To search for a specific permission it is possible to use the search bar under the permission headline.
{% hint style="info" %}
**Note:** System administrators have all permissions by default. This can not be changed.
{% endhint %}
---
# 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.struct.com/tutorials/guides/how-to-work-with-user-management/how-to-set-up-a-role.md?ask=&goal=
```
`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.