> 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/create-new-role.md).
# Create New Role
To create a new role, it's important to ensure you are in the Cockpit menu and then click on Administration. Then Click on Roles.
The page will open on all the roles already created.\
Create New Role
1. **Create a New Role:**\
Click on **Create Role** in the top-left corner of the page.
2. **Enter Role Name:**\
Provide a name for the new role in the designated field.
3. **Edit Role Permissions:**\
Click on the **⋮ (ellipse)** icon of the created role and select **Edit**.
4. **Assign Permissions:**\
Mark the checkboxes to assign specific permissions to the role.
5. **Save the Configuration:**\
Click **Save** to finalize the role creation and permissions.
{% hint style="info" %}
When creating a new role, it’s best to group permissions from similar categories, such as a 'viewer role' with viewing rights across all categories, or a 'full administration role' with all user-related permissions. This keeps things clear, manageable, and secure.
{% 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 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/create-new-role.md?ask=&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.
