> For the complete documentation index, see [llms.txt](https://docs.thewalletcrew.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.thewalletcrew.io/guides-monitoring/monitor/pass-list.md).

# Pass list

The pass list shows every pass in a programme. Use it to find a pass by any identifier, filter by template or date, and open the pass detail page for a full view of that pass's history.

<details>

<summary><strong>Real-world examples</strong></summary>

* A support agent searches a loyalty number to answer a customer query.
* An operations manager filters by template and creation date to check a batch issue.
* A programme administrator opens a pass to verify its current state and history.

</details>

## How to open the pass list

The pass list is the starting point for finding and checking a pass. It brings every pass available in the account into one view.

{% stepper %}
{% step %}

### Open the back-office

Sign in to The Wallet Crew back-office.
{% endstep %}

{% step %}

### Go to **Wallet > Passes**

The list loads all available passes. By default, the newest updates appear first.
{% endstep %}
{% endstepper %}

## Finding a pass

The search and filter controls at the top of the list narrow the result set quickly. Start with the identifier already available in the customer case, then add template or date filters if needed.

**Filters available:**

* **Pass ID** — the internal platform identifier for the pass.
* **External ID** — any external identifier linked to the pass, such as a CRM customer ID, a loyalty number, or a booking reference. This is the most common way support teams locate a specific customer's pass.
* **Pass template** — narrows the list to passes created from one template.
* **Metadata fields** — filters by any metadata field defined on the passes, such as `storeId` or `programmeId`. These fields depend on the programme setup and can vary from one programme to another.
* **Creation date** — shows only passes created within a date range.
* **Last updated** — shows only passes updated within a date range.

{% hint style="info" %}
To find a pass for a specific customer, filter by **External ID** using the identifier sent when the pass is created — for example, a CRM ID, loyalty number, or booking reference.
{% endhint %}

## Columns

The default columns give a quick operational view of each pass.

| Column              | What it shows                                       |
| ------------------- | --------------------------------------------------- |
| Pass ID             | The internal platform identifier                    |
| Creation date       | When the pass record was created                    |
| Last updated        | When the pass was last modified or updated          |
| Template            | Which pass template the pass was created from       |
| External ID         | The external identifiers linked to this pass        |
| Installation status | Whether the pass is currently installed in a wallet |

Use the column selector to add or remove columns. Metadata fields are available as extra columns, and the selected layout is saved in the browser.

## Opening a pass

Click any row in the list to open the pass detail page for that pass.

For what can be reviewed once the pass is open, see [Pass details](/guides-monitoring/monitor/pass-details.md).

## FAQ

<details>

<summary>Which filter should be used first for a customer case?</summary>

**External ID** is usually the fastest starting point. It matches the identifier sent from the source system when the pass was created.

</details>

<details>

<summary>Why does filtering by External ID show several rows for the same identifier?</summary>

The back-office shows every pass created with that External ID. An External ID does not guarantee a one-to-one match with a pass.

Multiple rows usually result from test enrolments or repeated API calls. To identify the active pass, check the **Installation status** column, then compare the most recent **Last updated** value.

For the technical model behind external identifiers and data retrieval, see [Pass data and sync](/developers-guides/pass-architecture/pass-data-and-sync.md).

</details>

<details>

<summary>Why do metadata filters differ between programmes?</summary>

Metadata fields come from each programme's pass setup. One programme may use `storeId`, while another may use `eventId` or `membershipTier`.

</details>

<details>

<summary>Why do the visible columns look different on another browser?</summary>

The column setup is saved in the local browser. A different browser or device can show a different saved layout.

</details>


---

# 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.thewalletcrew.io/guides-monitoring/monitor/pass-list.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.