> 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/customer-self-service/overview/customer-portal-overview.md). # Customer Portal Overview The **customer portal** is your customer's signed-in, self-service home in PeakCommerce. It gives each account holder one place to manage their subscriptions, billing, account details, and support — without opening a ticket or waiting on a CSR. Because every screen is configurable, the portal you ship reflects your brand, your catalog, and the exact actions you want customers to be able to take on their own. This matters because self-service deflects support load while giving customers the control they expect. ## How it works Customers reach the portal at your portal domain and sign in through **Auth0** (or your own IdP / SSO if connected). After login they land on **My Subscription**, the default view of their active plans. From there they can move between the portal pages you've published. The portal is assembled from **Portal-type pages** built in [Content → Pages](/product/journeys-and-pages/pages.md). Each page is composed of configurable blocks — for example an account header, subscription cards, a billing summary, invoice history, payment methods, and usage meters — so you control what each customer sees and in what order. Self-service **actions** (change plan, add or remove add-ons, renew, cancel) don't run as hard-coded buttons; they execute as [Customer Self-Service journeys](/product/journeys-and-pages/journey-basics/journeys-overview.md). That keeps pricing, eligibility, and retention logic configurable rather than fixed — see [customer subscription management](/product/customer-self-service/subscription-management/customer-subscription-management.md) and the [retention journey](/product/customer-self-service/subscription-management/customer-retention-journey.md). ## Who it's for & admin view The portal is for your end customers. Admins can preview what a customer sees by opening the customer from the **user menu** (your name, bottom-left) → **Settings → Users** and using the impersonation / login-as option — useful for troubleshooting and CSR assistance. **Gotcha:** which actions a customer can take is gated by [portal action permissions](/product/using-peakcommerce/profiles-and-permissions/portal-action-permissions.md), so a published page may still hide or disable a control if the account's profile lacks it. ## Next steps * [What is the customer portal?](/product/customer-self-service/overview/what-is-the-customer-portal.md) * [Access the customer portal](/product/customer-self-service/overview/access-the-customer-portal.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/customer-self-service/overview/customer-portal-overview.md?ask=&goal= ``` `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.