> 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/creating-a-location.md).

# Creating a location

1. In the left menu, click **Locations**, or open the merchant's three-dot menu and select **Locations**.
2. Click **+ Create Location**. The **Create Location** window opens.
3. Check that the **Merchant** field shows the correct merchant.
4. Enter the **Location Name** and the **Location Number**. Both are required.
5. Optionally, enter a **Description** and a **Logo**.
6. Click **Save** at the bottom of the window.

<figure><img src="https://3556089516-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-MbqMA3Kf8t2xEX9F6y9%2Fuploads%2Fd7eQuaBwar60kvRKrmHL%2Fp-create-location.png?alt=media" alt="Create Location: Merchant, Location Name and Location Number"><figcaption><p>Create Location: Merchant, Location Name and Location Number</p></figcaption></figure>

**Use different details for the location (optional)**

A new location uses the merchant's details, such as its address and contact information. If the location has different details, select **Override Merchant Details**. The location fields become available: Display Name Override, Category, Locale, License ID, License Name, Location Email, Location Phone, Location Website, Location Address and Location Contact (Visible to consumers).

<figure><img src="https://3556089516-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-MbqMA3Kf8t2xEX9F6y9%2Fuploads%2FLfKuxoEBOpp2jeqSFcAy%2Fp-create-location-override.png?alt=media" alt="Override Merchant Details selected"><figcaption><p>Override Merchant Details selected</p></figcaption></figure>

The window also has **Payment Page Style** and **Configuration** sections, the same as for a merchant. When the location is saved, a **Success** message appears and the location is added to the list.

<figure><img src="https://3556089516-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-MbqMA3Kf8t2xEX9F6y9%2Fuploads%2FLtX5dAODfiAcSULdOamF%2Fp-location-created.png?alt=media" alt="The new location in the Locations list"><figcaption><p>The new location in the Locations list</p></figcaption></figure>

**The location menu**

The three-dot menu at the end of a location's row has these options: **Edit**, **Payment Methods**, **POS / Register**, **Transaction Templates**, **Branch API**, **Settings** and **Delete**. You use it in the next sections.

<figure><img src="https://3556089516-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-MbqMA3Kf8t2xEX9F6y9%2Fuploads%2FHvREsSiaxX1BmGVD6p2t%2Fp-location-menu.png?alt=media" alt="The location menu"><figcaption><p>The location menu</p></figcaption></figure>


---

# 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/creating-a-location.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.
