> For the complete documentation index, see [llms.txt](https://community.commandersact.com/adloop/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://community.commandersact.com/adloop/i-start-your-adloop-discovery/basic-informations/users-and-administrators.md).

# Users and Administrators

### Users in Adloop

There are 3 levels of access in Adloop: User, Dataset Administrator and Responsible Administrator.

**User** : Has access to the Datasets to which they have been invited and can use the Reporting, Export and Notifications features. However, they cannot create Data Sources or Destinations or manage data or act on other Users.

**Dataset Administrator** : has full access to all features in the Dataset(s) for which he is the Administrator. He can create new Users or Administrators in the context of the Dataset.

**Main Administrator** : has full access to the entire Workspace for which he is responsible. He manages the billing and can create new Datasets.

### Details of user rights in Adloop

| **Functionalities**      | **Users** | **Dataset Administrator** | **Main Administrator** |
| ------------------------ | --------- | ------------------------- | ---------------------- |
| REPORTS                  |           |                           |                        |
| Saved reports            |           |                           |                        |
| New reports              |           |                           |                        |
| DATA MANAGEMENT          |           |                           |                        |
| Data sources             |           |                           |                        |
| Metrics and KPIs         |           |                           |                        |
| Dimensions               |           |                           |                        |
| Matching                 |           |                           |                        |
| EXPORT CENTER            |           |                           |                        |
| Exports                  |           |                           |                        |
| Export destination       |           |                           |                        |
| NOTIFICATION CENTER      |           |                           |                        |
| Notifications            |           |                           |                        |
| Notification destination |           |                           |                        |
| ADMINISTRATION           |           |                           |                        |
| Users                    |           |                           |                        |
| Datasets                 |           |                           |                        |
| Subscribing / Billing    |           |                           |                        |


---

# 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://community.commandersact.com/adloop/i-start-your-adloop-discovery/basic-informations/users-and-administrators.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.