> For the complete documentation index, see [llms.txt](https://docs.hollaex.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.hollaex.com/how-tos/operator-control-panel/roles.md).
# Roles
{% hint style="success" %}
Enterprise operators have access to a more specialized version of roles, such that they can fine-tune the access and permissions for larger teams. [This can be found at the following doc page.](/how-tos/operator-roles.md)
{% endhint %}
From this page, you can designate operator roles. You can invite other exchange operators and specify their roles to help manage the exchange. Each role has a different level of access and thus operations possible on your exchange. You can assign operator roles by simply clicking the ‘Add operator’ button.
## Role Types
1\. **Administrator -** Can access all areas of the operator controls such as coin creation, minting & burning, trading pairs, and designation of other operator roles.
2\. **Supervisor** - Can access all deposit, withdrawals, and approval settings.
3\. **KYC Role** - Can access required user data to review KYC requirements.
4\. **Communicator** - Has access to website editing tools, with control over aspects such as visuals and text.
5\. **Support**- Can access required user information for user verification.
---
# 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.hollaex.com/how-tos/operator-control-panel/roles.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.