> 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/adding-sensepass-tags.md).

# Adding SensePass tags

By default, SensePass registers the tags it sends you, and they appear in the **Serial** list. You can also add tags yourself in **Management** > **SensePass Tags**. The page lists the tags with their Serial, Type, Pairing Code, Merchant Name, Location Name, POS Name, Status and Created date.

**Add one tag**

1. Open **Management** > **SensePass Tags** and click **Create Tag**.
2. Select the **Pairing Mode**, then enter the **Serial** or click **Scan** to scan the tag.
3. Select the **Type**, for example **POS Paired**.
4. Click **Save**.

<figure><img src="https://3556089516-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-MbqMA3Kf8t2xEX9F6y9%2Fuploads%2FDBDm0PaYTg2pSJ5m0kuM%2Fp-create-tag.png?alt=media" alt="Create Tag window"><figcaption><p>Create Tag window</p></figcaption></figure>

**Add several tags**

1. Click **Create Multiple Tags**.
2. In step 1, **Details Selection**, select the **Merchant** and **Location**, then click **Next**.
3. In step 2, **Multiple Scan**, scan the tags one after the other, then save.

<figure><img src="https://3556089516-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-MbqMA3Kf8t2xEX9F6y9%2Fuploads%2FPps6FQ3QMd06Ykqxj24p%2Fp-multi-tags.png?alt=media" alt="Create Multiple Tags, step 1"><figcaption><p>Create Multiple Tags, step 1</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/adding-sensepass-tags.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.
