> For the complete documentation index, see [llms.txt](https://docs.cloudio.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.cloudio.io/managing-roles-and-users/working-with-roles-and-users/creating-a-user/assigning-a-role-to-the-user.md).

# Assigning a role to the user

After a user is created, the administrator can assign roles to the user for controlling the access to the application components.

1. In the upper right corner of the CloudIO homepage, in the menu bar,  click![](/files/-M-mqQrhvyhl1QdlDK3f).  The **Navigation** page is displayed.

![](/files/-M01ZNiqggPWG-1n4yax)

2\. Under the **Administration** role, click **Manage Users.**

The **Manage Users** page is displayed.

![](/files/-M02DC0Rqbd-bTyJGO4Q)

3\. Click on the required user.

The **User Details** page is displayed.

![](/files/-M02DvoSTUDQKQ7y5ver)

4\. In the upper right corner of the **User Details** section, click **Next**.

The roles page is displayed.

![](/files/-M02HXMfYdrne-N53vb1)

5\. In the upper right corner of the **User Roles** section, click **Add Role** and in the role column, select the role to be assigned to the user.

6\. Enter the details for the role and click **Save**. The user is assigned to the role.


---

# 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://docs.cloudio.io/managing-roles-and-users/working-with-roles-and-users/creating-a-user/assigning-a-role-to-the-user.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.