> 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/getting-started/project-prep/3.-org-provisioning-and-adding-users.md).

# 3. Org Provisioning & Adding Users

Before anyone can explore PeakCommerce or start configuration, your organization needs its own tenant and your team needs sign-in access. This step gets both in place.

**Provisioning your org**

Your PeakCommerce org (tenant) is provisioned automatically around the start date of your contract. Your designated administrator receives an email invitation to claim it — click the link and follow the prompts to set up the account. Sign-in is handled by **Auth0**, so you'll be prompted to set your own password; PeakCommerce never sees or stores it directly.

**Who and when:** for security, only your designated admin should claim the org and set up the initial account. Everyone else joins by invitation afterward.

**Adding your team**

Once you're signed in, the admin invites everyone who needs access — including your PeakCommerce project team members — so the org is ready for collaboration:

1. Open the **user menu** (your name, bottom-left) → **Settings → Users**.
2. Click **Add User** (top right).
3. Enter the person's details and assign them a **Role** and a **Profile**.

Each user gets two settings that work together. The **Role** — **Admin**, **CSR**, **Partner**, or **Customer** — sets which portal they land in and their broad experience. The **Profile** fine-tunes exactly what they can see and do within that role. New users receive an Auth0 email to set their own password, so you never handle credentials for them. You can add or remove users from **Settings → Users** at any time.

**Gotcha:** the role alone doesn't grant detailed permissions — the profile does. A teammate with the right role but a thin profile may still be missing access they expect, so pick the profile deliberately. For the full picture, see [Users & User Roles](/product/using-peakcommerce/users-and-user-roles.md).

**Next step →** With your team in place, learn how help works in [Intro to Support](/product/getting-started/project-prep/4.-intro-to-support.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 by asking a question.

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

```
GET https://docs.peakcommerce.com/product/getting-started/project-prep/3.-org-provisioning-and-adding-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.