> 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/administrator-users.md).

# Administrator Users

Administrator users are the people who build and run your tenant. The **Admin** role gives broad configuration access, so it's the role you assign to employees who set up the catalog, design journeys, wire up integrations, and manage other users. Because admins can change how the whole platform behaves, keep this group small and scope each admin with a profile.

## How to create one

Open the **user menu** (your name, bottom-left) → **Settings → Users**, click **Add User**, set **Role** to **Admin** and choose an Administrator **profile**. The admin receives an Auth0 email to set their own password — you never set it for them.

## What admins can do

With the Admin role, a user can reach platform configuration — catalog and offers, content (pages and components), journeys, integrations and API keys, users and profiles, audit logs, and tenant settings. Admins do *not* carry an **External Account** link; that field is only for Customer and Partner users tied to a billing account.

## Scope each admin with a profile

The role grants the *area* of access; the **profile** decides exactly what each admin can see and do. Pair the Admin role with a permission profile to limit one admin to, say, content and journeys while another manages billing and integrations. Don't rely on the role alone — two admins with different profiles can have very different reach.

**Who and when:** assign Admin to trusted internal staff who configure the platform, not to people who only assist customers (use **CSR** for that).

See [User Roles](/product/using-peakcommerce/users-and-user-roles/user-roles.md), [Profiles & Permissions](/product/using-peakcommerce/profiles-and-permissions.md), and [Authentication & Security](/product/using-peakcommerce/authentication-and-security.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/administrator-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.