> 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/10.2-analytics/pentaho-user-console/about-pentaho-user-console-perspectives/administration/manage-users-and-roles-in-puc.md).

# Manage Users and Roles in the User Console

You can use the Users & Roles page within the Administration perspective of the Pentaho User Console (PUC) to manage users and their roles in the system.

You have access to default assignments for users and roles to use as templates when setting up your actual users and roles. You must log in to the User Console as an administrator (or be assigned to a role that has the Administer Security permission) to manage users and roles for Pentaho Security.

You can control users and roles in the User Console with the point-and-click user interface. Use the **Users & Roles** page to switch between user and role settings. You can add, delete, and edit users and roles from this page.

Access to files or folders can also be refined using the **Browse Files** perspective in the User Console. Each file or folder can use the default permissions or permissions can be customized for specific users and roles. For additional security in multi-tenancy organizations, you can hide individual users' Home folders. See the **Administer Pentaho Data Integration and Analytics** document for more information.


---

# 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/10.2-analytics/pentaho-user-console/about-pentaho-user-console-perspectives/administration/manage-users-and-roles-in-puc.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.
