> For the complete documentation index, see [llms.txt](https://docs.controlbee.nl/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.controlbee.nl/controlbee-docs/en/uitvoeren/rollen.md).
# Roles
Assign responsibilities with roles, knowledge, competencies, and authorities
To put the processes with associated evidence into practice and maintain them properly, responsibilities are assigned.
Examples of roles include: management, security officer, or HR employee.
## Create role
A role can be created by clicking 'new' in the roles overview. In addition to a name and description, version control is available to manage changes. A URL can also be added, so that the user can reach, for example, the job descriptions within their own user environment with one click.
## Link knowledge, competencies, authorizations and evidence to a role
For each role, the knowledge and competencies can be determined and the evidence can be linked. This records what a specific role needs in terms of knowledge and competencies, and what authorizations that role has. You can also link evidence to each role and indicate for each piece of evidence which role type it belongs to.
{% hint style="info" %}
Role types can only be created by the administrator.
{% endhint %}
## Unlink and edit
By clicking the dots, you can unlink or edit knowledge, competencies, authorizations and evidence for a role.
---
# 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.controlbee.nl/controlbee-docs/en/uitvoeren/rollen.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.
