> 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-scan/scan/pass-scanner/pass-scanner-profiles.md).

# Pass Scanner profiles

Create Pass Scanner profiles: reusable scan contexts that decide which benefits a device accepts, whether staff can add stamps, and when the profile is open.

A profile is a reusable scan context, such as "Bar", "Breakfast", "Cloakroom" or "Gate F". It tells Pass Scanner which benefits to accept, whether staff can add stamps, how long to ignore a second scan of the same pass, and when the profile can be used. Profiles are created once, then assigned to as many devices as needed.

Profiles keep staff focused and prevent mistakes.

<details>

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

* **Festival bar:** a "Bar" profile accepts only benefits tagged `drinks`, with a 5-second repeat-scan block to avoid double use.
* **Hotel breakfast:** a "Breakfast" profile accepts the "Breakfast included" benefit template and opens every day at 7:00 for 210 minutes.
* **Coffee shop counter:** a "Counter" profile accepts benefits tagged `member` or `reward` and the "Barista workshop pack", and lets staff add stamps to stamp cards.
* **Coffee shop workshops:** a "Saturday workshops" profile accepts only the "Barista workshop pack" and opens every Saturday at 9:00 for 120 minutes.
* **Stadium gates:** a "Gate F" profile is valid only on match days, from its **Valid from** to its **Valid until** date.
* **Pop-up store:** a "Launch week" profile accepts the launch gift template only during the opening week.

</details>

## How profiles work

Each device can run one or several profiles. When a device has several, staff pick one in Pass Scanner from **Choose a profile**, which starts a **session**. A profile outside its opening windows is shown as **Not open now**.

```mermaid
flowchart LR
    P1["Profile: Bar<br/>tags: drinks"] --> D1["Device: Bar phone"]
    P2["Profile: Counter<br/>stamps allowed"] --> D2["Device: Counter phone"]
    P2 --> D3["Device: Spare phone"]
    P3["Profile: Breakfast<br/>7:00, 210 min"] --> D3
    D3 -->|staff pick one| S["Session"]
```

The phone applies the profile: it filters the benefits shown after a scan. A device with no profile accepts every benefit with **Show in Pass Scanner** switched on.

## Create a profile

Profiles are managed from **Settings → Access control → Device profiles**. The list shows each profile's name, schedule and what it accepts.

<figure><img src="https://2365162339-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FiqBD4M0nHFMaFeKR75p9%2Fuploads%2Fgit-blob-a7a1ab633668eabc98d81266044426358f8af749%2Fdevice-profiles-list-single-frame.png?alt=media" alt="The Device profiles list shows each profile&#x27;s schedule and what it accepts, here the loyalty and reward tags."><figcaption><p>The Device profiles list shows each profile's schedule and what it accepts: tags, benefit templates and stamps.</p></figcaption></figure>

{% stepper %}
{% step %}

### Open the editor

Open **Settings → Access control → Device profiles**, then click **Add new**.

<p align="center"><a href="https://admin.thewalletcrew.io/tenant/~/settings/access/device-profiles" class="button secondary" data-icon="chevrons-right">Open Device profiles in the admin console</a></p>
{% endstep %}

{% step %}

### Identify it

Give the profile a **Name**, an optional **Description**, and an icon and a color that staff will recognize on the phone.
{% endstep %}

{% step %}

### Choose what it accepts

In **Benefit filter**, select the tags and the benefit templates the profile accepts. Leave both empty to accept every benefit.
{% endstep %}

{% step %}

### Set stamps, repeat-scan block and schedule

Decide whether staff can add stamps, how long a second scan of the same pass is ignored, and when the profile is open.
{% endstep %}

{% step %}

### Save and assign it

Click **Save**, then add the profile to devices from their **Profiles** card in [Manage devices](https://docs.thewalletcrew.io/guides-scan/scan/pass-scanner/manage-devices.md).
{% endstep %}
{% endstepper %}

<figure><img src="https://2365162339-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FiqBD4M0nHFMaFeKR75p9%2Fuploads%2Fgit-blob-4bf5df3b2a41f6a2d9aac47b7714033ff0c48c88%2Fdevice-profile-benefit-filter-retake.png?alt=media" alt="Benefit filter of a new device profile with the loyalty and reward tags selected, and the benefit templates they cover"><figcaption><p>The Counter profile accepts the benefits tagged loyalty or reward.</p></figcaption></figure>

### Identity

| Setting            | Description                                                                                      |
| ------------------ | ------------------------------------------------------------------------------------------------ |
| **Name**           | Required, up to 200 characters. Shown to staff when they pick a profile.                         |
| **Description**    | Optional, up to 500 characters.                                                                  |
| **Icon and color** | An emoji and a color shown on the phone, so staff can tell at a glance which profile is running. |

### Benefit filter

The benefit filter decides which benefits Pass Scanner offers after a scan. A benefit is accepted when it carries one of the selected **Tags** or comes from one of the selected **Benefit templates**. When nothing is selected, the profile accepts every benefit.

A benefit template already covered by a selected tag is ticked and grayed out with **via #tag**, for example **via #reward**, so the editor shows the full list of what the profile accepts. The profiles list sums it up in its **Accepts** column, with **Stamps** when staff can add stamps.

Only benefit templates with **Show in Pass Scanner** switched on are listed. A profile can select up to 50 tags and 200 benefit templates. Tags are set on [benefit templates](https://docs.thewalletcrew.io/guides-animation/engage-and-animate/benefit-templates.md), which makes them the easiest way to build a filter that keeps working when new templates are added: tag every drink benefit `drinks`, and the "Bar" profile accepts new drink benefits automatically.

{% hint style="info" %}
When a selected benefit template is deleted, the profile shows **To review**. The missing template is left out of the filter and removed when the profile is saved. If nothing remains in the filter, the profile accepts every benefit.
{% endhint %}

{% hint style="info" %}
**Benefit templates are in beta.** Switch on **Beta features** in the profile menu, at the top right of the admin console, to see **Engagement → Benefit templates**.
{% endhint %}

### Stamp card

**Staff can add stamps** lets staff add a stamp when they scan a [stamp card](https://docs.thewalletcrew.io/guides-design/design/stamp-card.md). It is off by default: when off, scanning a stamp card only shows it.

### Repeat scan block

**Repeat scan block (seconds)**, under **Advanced settings**, is how long the device ignores a second scan of the same pass, between 0 and 3,600 seconds, 5 by default. It prevents a benefit or a stamp from being used twice when a pass stays in front of the camera. Set it to 0 to turn the block off.

### Schedule

The schedule limits when the profile can be used.

| Setting                         | Description                                                                                                                                                                               |
| ------------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| **Valid from**, **Valid until** | Optional dates outside of which the profile cannot run.                                                                                                                                   |
| **Opening windows**             | Up to 20 windows. Each window opens at the time set and stays open for its duration, from 1 to 1,440 minutes. With no window, the profile is open all the time within its validity dates. |

Each opening window repeats **Every** year, month, week, day, hour or minute, at a chosen time, and stays open for its **Duration (minutes)**. A weekly window can be limited to some days of the week. The editor summarizes each window in plain words, for example "At 09:00, only on Saturday · 2h". Opening windows are evaluated in the **phone's local time**, not in the time zone of the admin console: a window set to open at 7:00 opens at 7:00 where the phone is.

<figure><img src="https://2365162339-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FiqBD4M0nHFMaFeKR75p9%2Fuploads%2Fgit-blob-be4fe03c43dc6b6d74f77f8808ad03a2817a2840%2Fdevice-profile-schedule-window-retake.png?alt=media" alt="Schedule card with the validity dates and one opening window every day at 9:00 for 120 minutes"><figcaption><p>The Schedule card holds the validity dates and the opening windows.</p></figcaption></figure>

When the schedule ends during a session, the session is closed with the end reason **Profile schedule ended**.

## Edit or delete a profile

Editing a profile updates every device that runs it: connected phones apply the change within seconds, and other phones at their next connection. A profile cannot be deleted while a device still lists it; remove it from those devices first.


---

# 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.thewalletcrew.io/guides-scan/scan/pass-scanner/pass-scanner-profiles.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.
