> 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/administration/partner-realms.md).

# Partner Realms

### Overview

Partner realms offer the ability to assign customer cohorts to a partner to manage within PeakCommerce.

For example, I may have territories assigned to partners based on geographic location of the customer. In this case we will use Northwest, and Southwest as two distinct territories.

Partner NW manages the Northwest customers and Partner SW manages the customers residing in the Southwest.

I would create two distinct partner realms:

| Realm           | Partner    |
| --------------- | ---------- |
| Realm Northwest | Partner NW |
| Realm Southwest | Partner SW |

When Partner NW logs into the partner portal to manage their account, they will have access to all customers assigned the role defined in the Realm Northwest. Similarly, when Partner SW logs into the partner portal to manage their account, they will have access to all customers assigned the role defined in the Realm Southwest

For more information on creating partner realms, view the Creating Partner Realms article.


---

# 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/administration/partner-realms.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.