> For the complete documentation index, see [llms.txt](https://docs.jentis.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.jentis.com/getting-started/quickstart/invite-your-team-user-permissions.md).

# Invite Your Team - User Administration

Welcome to our comprehensive guide on the access permissions of JENTIS.

This guide provides an overview of user permissions and user administration. Whether you are looking to manage account access, assign admin roles, or configure user permissions, follow the instructions below to configure your organization's settings. 

{% hint style="warning" %}
Administrators can view all user permissions across the organization. All other roles can only view users with permission levels equal to or lower than their own (e.g., an Analyst can view Read-Access users, but cannot view Administrators).
{% endhint %}

| Permission Group  | Description                                                                                       | Restrictions                                            |
| ----------------- | ------------------------------------------------------------------------------------------------- | ------------------------------------------------------- |
| ADMIN             | The admin is the highest permission group a customer can have.                                    | Cannot delete containers.                               |
| ANALYST (default) | Currently, ANALYST/TRACKING/TECHNICIAN have the same rights and do not differ in any way.         | Admin restrictions + cannot create/update/delete users. |
| TRACKING          | Currently, ANALYST/TRACKING/TECHNICIAN have the same rights and do not differ in any way.         | Admin restrictions + cannot create/update/delete users. |
| TECHNICIAN        | Currently, ANALYST/TRACKING/TECHNICIAN have the same rights and do not differ in any way.         | Admin restrictions + cannot create/update/delete users. |
| REPORTER          | A REPORTER can only navigate through the UI, can open the debug monitor, but cannot publish.      | Cannot modify anything but can read everything          |
| READACCESS        | A user with READACCESS can only navigate through the UI and cannot open the debug monitor.        | Cannot modify anything + cannot open preview monitor    |
| RESTRICTED        | A user with RESTRICTED is allowed to log into the JENTIS DCP, but can not navigate through the UI | Cannot navigate at all.                                 |


---

# 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.jentis.com/getting-started/quickstart/invite-your-team-user-permissions.md?ask=<question>&goal=<user_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.