> For the complete documentation index, see [llms.txt](https://docs.g-iot.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.g-iot.io/platform-user-guide-book/administration/role.md).

# Role

The GIoT Platform offers predefined roles to the users, to simplify their management. Only users with the appropriate permission can create new roles or modify existing ones.

Role It’s a set of permissions from different categories that defines what actions a user is allowed to perform within the platform.

The amount of the permissions in the role and the number of users assigned to that role are visible under the role name. Let’s see all the available roles:

* SuperAdmin: it has the highest permission, it’s allowed to access and modify every user’s information as well as request password update;
* Normal Access: it’s allowed to access to most of the functions and user’s information;
* Read only: it has access to all the functions but it’s unable to modify or export data;
* Custom Role: SuperAdmin or granted roles can easily create new roles;
* No create/No delete: it can’t either create, delete or modify roles.


---

# 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.g-iot.io/platform-user-guide-book/administration/role.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.