> For the complete documentation index, see [llms.txt](https://carare.gitbook.io/mint-mapping-service/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://carare.gitbook.io/mint-mapping-service/users-and-organisations/roles.md).

# Roles

Within MINT users will have one of the following roles:&#x20;

* Administrator – can create/update/delete users and child organisations for the organisation s/he is administering
* Annotator – can upload data for his/her organisation, view items, create mappings, etc.&#x20;
* Annotator, publisher – has the rights of an annotator and also the right to publish the data
* Data viewer – has only data viewing rights for his/her organisation

Users may be assigned to an organisation without a role, but until a role is assigned they will have very limited access to MINT.

{% hint style="info" %}
Note: There are also super-users who have full rights to all organizations and their data to enable them to provide support.
{% 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://carare.gitbook.io/mint-mapping-service/users-and-organisations/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.
