> For the complete documentation index, see [llms.txt](https://docs.peakcommerce.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.peakcommerce.com/product/using-peakcommerce/users-and-user-roles/viewing-your-users-list.md).

# Viewing Your Users List

The users list is your single roster of everyone with access to the tenant — admins, CSRs, partners, and customers — and the starting point for editing, deactivating, or impersonating any of them. It's where you confirm who has access, at what level, and whether their account is active.

## Open the list

Open the **user menu** (your name, bottom-left) → **Settings → Users**. Each row shows:

* **User** — avatar, name, and email, with a small dot indicating active status.
* **Role** — Admin, CSR, Partner, or Customer.
* **Profile** — the permission profile assigned to the user (see [User Profile Overview](/product/using-peakcommerce/profiles-and-permissions/user-profile-overview.md)).
* **Status** — a pill showing **Active** or inactive.
* **External Account** — the linked billing/identity account, shown for customers and partners.
* **Created** — when the user was added.

## Find and manage users

Use the search box to filter by **email** or **profile name**. Each row's menu (**⋯**) lets you **View**, **Edit**, **Impersonate** ("Log in as"), or **Delete** the user; click the row itself to open the full detail page with its Activity, Logins, and Impersonations tabs.

## Gotchas

* Search matches email and profile name — not display name — so search by email address when looking for a specific person.
* The Status dot and pill reflect platform access; a customer can still appear here as inactive if they were deactivated in the billing system.
* See [User Roles](/product/using-peakcommerce/users-and-user-roles/user-roles.md) to understand what each role column value implies.


---

# 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.peakcommerce.com/product/using-peakcommerce/users-and-user-roles/viewing-your-users-list.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.