> For the complete documentation index, see [llms.txt](https://docs.pentaho.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.pentaho.com/pba/9.3-analytics/pentaho-user-console/about-pentaho-user-console-perspectives/administration/manage-users-and-roles-in-puc/assign-roles-to-users.md).

# Assign Roles to Users

Use this task to assign roles to users in the Pentaho User Console

1. Make sure the **Manage Roles** tab is selected, then click the role in **Roles** list that you want to associate with a user or users.
2. In the **Available** list, click the user or users that you want to associate with that role.
3. Click the Right Arrow (>) to move the users to the **Selected** list. You can click the Double-Right Arrow (>>) to move all users from the **Available** list to the **Selected** list.
4. You can remove users from the **Selected** list by highlighting that user and clicking on the Left Arrow (<).

   The user moves from the **Selected** list to the **Available** list, and no longer has the permissions associated with that role. The users that appear in the **Selected** list are now tied to the highlighted role and have all of the permissions associated with that 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.pentaho.com/pba/9.3-analytics/pentaho-user-console/about-pentaho-user-console-perspectives/administration/manage-users-and-roles-in-puc/assign-roles-to-users.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.
