> 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/authentication-and-security.md).

# Authentication & Security

PeakCommerce secures every sign-in through **Auth0** as its identity provider, then governs what each signed-in person can see and do through roles and profiles. Authentication answers *who are you?*; [roles](https://docs.peakcommerce.com/product/using-peakcommerce/users-and-user-roles/user-roles.md) and [profiles](https://docs.peakcommerce.com/product/using-peakcommerce/profiles-and-permissions/user-profile-overview.md) answer *what are you allowed to do?* — keeping the two separate is what lets you adopt enterprise SSO without re-modelling permissions.

* **Sign-in** runs on Auth0 Universal Login — staff (Admins and CSRs) and customers alike. Social and enterprise SSO are supported.
* **Password and MFA policy** are enforced by Auth0, or by your own identity provider when you bring one.
* **End customers** can be signed into the customer portal automatically from your own app via SSO (operator-configured).
* **Administrative changes** are recorded in the audit log (**Settings → Audit Logs**).

Explore this section:

* [Single Sign-On for PeakCommerce Sites](https://docs.peakcommerce.com/product/using-peakcommerce/authentication-and-security/single-sign-on-for-peakcommerce-sites.md)
* [Login Pages](https://docs.peakcommerce.com/product/using-peakcommerce/authentication-and-security/types-of-login-pages-for-your-peakcommerce-account.md)
* [What Your Web Team Needs for SSO](https://docs.peakcommerce.com/product/using-peakcommerce/authentication-and-security/what-will-our-web-team-need-to-do-over-and-above-the-sso-setup.md)
* [Session Management](https://docs.peakcommerce.com/product/using-peakcommerce/authentication-and-security/session-management.md)
* [Password Policies](https://docs.peakcommerce.com/product/using-peakcommerce/authentication-and-security/understanding-and-configuring-password-policies-in-peakcommerce.md)
* [Viewing Audit Logs](https://docs.peakcommerce.com/product/using-peakcommerce/authentication-and-security/viewing-audit-logs.md)
* [Security and Data Protection](https://docs.peakcommerce.com/product/using-peakcommerce/authentication-and-security/security-and-data-protection.md) — how PeakCommerce protects your data and connected systems


---

# 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/using-peakcommerce/authentication-and-security.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.
