> 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.md).

# Users & User Roles

Everyone who signs in to your PeakCommerce tenant — your own staff, your resellers, and your end customers — is a **user**. Managing users well is how you control who can configure the platform, who can act on customer accounts, and who can only see their own subscription. Get it right and the platform stays secure and tidy; get it wrong and people see too much or too little.

You manage users from the **user menu** (your name, bottom-left) → **Settings → Users**. Click **Add User** to invite someone. Each user has two settings that work together:

* A **Role** — one of **Admin**, **CSR**, **Partner**, or **Customer** — which sets the broad experience and portal they land in.
* A **Profile** — which fine-tunes exactly what they can see and do within that role.

Sign-in is handled by **Auth0**: new users receive an email to set their own password, so you never handle passwords directly.

**Start here**

* [User Roles](/product/using-peakcommerce/users-and-user-roles/user-roles.md) — what each role is for
* [Administrator Users](/product/using-peakcommerce/users-and-user-roles/administrator-users.md) · [Customer Users](/product/using-peakcommerce/users-and-user-roles/customer-users.md) · [Partner Users](/product/using-peakcommerce/users-and-user-roles/partner-users.md)
* [Creating a new user](/product/using-peakcommerce/users-and-user-roles/creating-a-new-user.md) · [Editing a user](/product/using-peakcommerce/users-and-user-roles/editing-a-user.md)
* [Profiles & Permissions](/product/using-peakcommerce/profiles-and-permissions.md)


---

# 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.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.