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

# Partner Portal Overview

The Partner Portal gives your channel partners — resellers, agencies, and referral partners — a dedicated, co-branded workspace to manage the customers assigned to them and their own account. Partners are a **role type** in PeakCommerce: they sign in to a focused portal rather than the full admin app, and everything they see is scoped to their book of business. This lets you run an indirect sales channel without giving partners visibility into other partners' customers or your internal operations.

## Key concepts

* **Partner role** — a user whose portal type is *Partner*. The role determines which portal they land in and which permissions apply.
* **Assigned accounts** — the cohort of customer accounts a partner can see and act on. Assignment is driven by **Territory Rules** and/or manual assignment (see [Partner Administration](/product/partner-portal/administration.md)).
* **Partner Channel** — the admin-side area (sidebar group) where staff configure and monitor the channel: **Commission Structures** and **Channel Analytics**.

## What a partner does

* **Manage assigned customers** — view each assigned account's contacts, subscriptions, and invoices, and make subscription changes on the customer's behalf.
* **Change and cancel subscriptions** — within the limits of their permissions (see *Who can do what* below).
* **Manage their own subscription** — partners with their own billing account can view and manage it under *My Subscription*.
* **See performance and earnings** — partners can review their accounts and commissions; staff see channel-wide totals and a partner leaderboard under **Channel Analytics**.

## Who can do what

A partner's access is scoped by their **partner profile** (record access limited to accounts assigned to them) and by **portal-action permissions** — change-plan and cancel-plan are *separate* grants, so you can let a partner upgrade/downgrade plans without allowing cancellations, or vice versa. See [Portal Action Permissions](/product/using-peakcommerce/profiles-and-permissions/portal-action-permissions.md) and [Partner Users](/product/using-peakcommerce/users-and-user-roles/partner-users.md).

## Gotchas

* A partner sees an account **only** once it's assigned to them — a customer with no matching Territory Rule and no manual assignment is invisible to every partner.
* Change vs. cancel are independent. If a partner can't cancel, confirm the cancel-plan permission, not just change-plan.

## Setting up partners

1. Create partner users with the **Partner** role and a partner profile ([User Roles](/product/using-peakcommerce/users-and-user-roles/user-roles.md)).
2. Assign each partner their customers — see [Assigning Accounts to Partners](/product/partner-portal/administration/partner-realms.md).
3. Configure earnings under **Partner Channel → Commission Structures**.

## Related

* [Partner Administration](/product/partner-portal/administration.md)
* [Customer Management](/product/partner-portal/customer-management.md)
* [Partner Users](/product/using-peakcommerce/users-and-user-roles/partner-users.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/partner-portal/partner-portal-overview.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.