> 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/pentaho-data-mastering/managing-users-and-roles/viewing-users.md).

# Viewing users

View the list of users to see who can access the Pentaho Data Mastering application.

You must have admin privileges to view users.

Perform the following steps to view users:

1. On the left navigation menu, click **Master Data**. The **Master Data** page opens.
2. In the **Users** card, click **Users**.

   The Users page opens with the list of users shown in a table that contains the following information:

   | Field          | Description                                                          |
   | -------------- | -------------------------------------------------------------------- |
   | **ID**         | User ID generated by the system.                                     |
   | **Names**      | Name of the user.                                                    |
   | **Roles**      | Role assigned to the user. If no role is assigned, then NA is shown. |
   | **Created At** | Date and time of user creation.                                      |


---

# 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.pentaho.com/pentaho-data-mastering/managing-users-and-roles/viewing-users.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.