> For the complete documentation index, see [llms.txt](https://docs.sensepass.com/sensepay/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.sensepass.com/sensepay/partners/partner-dashboard/how-sensepass-partners-is-organized.md).

# How SensePass Partners is organized

Every account is organized in levels: **Merchants**, their **Locations** and, in physical locations, **POS / Registers** with their devices (SensePass tags and/or card terminals). A merchant is the business. A location is one store, branch or other unit of that business. Each merchant has one or more locations.

| Item                   | Belongs to                 | What it is                                                                          |
| ---------------------- | -------------------------- | ----------------------------------------------------------------------------------- |
| Merchant               | Your partner account       | The business account, for example Demo Coffee Co.                                   |
| Location               | A merchant                 | One store or unit, for example Downtown Store.                                      |
| Payment method         | A location                 | The processor or wallet the location accepts, with its credentials.                 |
| POS / Register         | A location                 | A checkout point in a physical location: Standalone or POS Paired.                  |
| SensePass tag          | A POS / Register           | The NFC / QR tag the customer taps or scans. Paired on the register.                |
| Card terminal (PinPad) | A POS / Register           | An EMV card reader, added as an EMV terminal for the register.                      |
| Backoffice user        | A merchant or one location | A person who signs in to the Merchant Dashboard.                                    |
| Branch API key         | A location                 | The key a POS or online store uses to send payments to SensePass for that location. |

When you set up a new merchant, follow this order: create the merchant, create its locations, configure payment methods, create registers, pair tags and/or add card terminals to each register, create users, and create API keys if the merchant connects a system by API.

Most screens show the selected merchant and location at the top of the page, for example **Demo Coffee Co - Downtown Store**. Click the arrow next to it to switch to another location.


---

# 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.sensepass.com/sensepay/partners/partner-dashboard/how-sensepass-partners-is-organized.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.
