> 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/partner-portal/customer-management.md).

# Customer Management

Partners use the portal to work their book of business: finding a customer fast, reviewing where each account and subscription stands, and — with the right permissions — acting on a customer's subscription.

Everything here is scoped to your assigned accounts. You only ever see and act on the accounts assigned to you through Territory Rules and manual grants, enforced on the server. What you can do (view, change, cancel) is set by your **Partner** profile.

In this section:

* [Account and Subscription Summary Reports](https://docs.peakcommerce.com/product/partner-portal/customer-management/account-and-subscription-summary-reports.md) — live account and subscription summaries pulled from billing.
* [Customer Search](https://docs.peakcommerce.com/product/partner-portal/customer-management/advanced-customer-search.md) — find an assigned account by name or number within a large cohort.

Related:

* [Partner Portal Overview](https://docs.peakcommerce.com/product/partner-portal/partner-portal-overview.md)
* [Assigning Accounts to Partners](https://docs.peakcommerce.com/product/partner-portal/administration/partner-realms.md)
* [Portal Action Permissions](https://docs.peakcommerce.com/product/using-peakcommerce/profiles-and-permissions/portal-action-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 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/partner-portal/customer-management.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.
