> 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/before-you-begin.md).

# Before you begin

This guide shows you how to set up a merchant in the SensePass Partners dashboard, from the merchant application to its first register, user and API key. The examples use a fictional demo merchant named **Demo Coffee Co** with one location named **Downtown Store**.

### What you need

* Your SensePass Partners login (username or email and password). If you do not have one, contact SensePass.
* The merchant's business details: license ID, legal and display name, address and a contact person.
* Your SensePass tags, if the merchant takes payments with tags.
* The payment processor credentials for the merchant, if you set up a payment method now.
* The name, phone number and email address of each user you want to add.

### Sign in

1. Open <https://partner.sensepass.com> in your web browser.
2. Enter your **Username / Email** and click **NEXT**.
3. Enter your **Password** and click **LOGIN**.
4. If you are asked to change your password, follow the steps on the screen.

### The left menu

The left menu has these items: **On Boarding**, **Merchants**, **Locations**, **POS / Register**, **Management** (SensePass Tags, EMV Terminals, Notifications, Backoffice Users, Payment Methods, Device Pairs, Billing, Ecom Integrations, Surcharge, Receipts, Security) and **Developer** (Merchant API, Branch API, Client ID, Transaction Templates, Terminal Agent).


---

# 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/before-you-begin.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.
