> 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/manage-devices.md).

# Manage devices

Register the phones allowed to run Pass Scanner, connect them with their QR code, assign profiles, follow their sessions and logs, and revoke access.

The **Devices (Pass Scanner)** page controls which phones are allowed to connect to Pass Scanner. Each device represents one scanner installation with its own credential.

## How device management works

Devices are managed from **Settings → Access control → Devices (Pass Scanner)**. The list shows each device's name, type, status and profiles. Viewing devices requires the permission to see devices, and creating, renaming, deleting or reconnecting them requires the permission to edit them (see [Users & roles](https://docs.thewalletcrew.io/configure/advanced-configuration/platform/user-access.md)).

Using one device per physical phone is the safest model. It keeps revocation precise, makes audits easier, and avoids sharing one credential across several teams.

### Add a new device

{% stepper %}
{% step %}

#### Create the device

Open **Settings → Access control → Devices (Pass Scanner)**, then click **Add new**.

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

{% step %}

#### Describe it

Give the device a clear **Name**, up to 200 characters, and an optional **Description** to identify the location, team or purpose of the phone. New devices are **Enabled** by default.
{% endstep %}

{% step %}

#### Choose its profiles

In **Profiles**, pick a profile in **Profile to add** and click **Add**, once per profile the device may run. The order is the order shown on the phone and can be changed later. A device without a profile accepts every benefit with **Show in Pass Scanner** switched on. **Manage profiles** opens the [Pass Scanner profiles](https://docs.thewalletcrew.io/guides-scan/scan/pass-scanner/pass-scanner-profiles.md) page.
{% endstep %}

{% step %}

#### Save and connect the phone

Click **Save**. The **Connection token** dialog opens with the connection QR code and a connection link. Then [connect the phone](https://docs.thewalletcrew.io/guides-scan/scan/pass-scanner.md#connect-the-phone-to-the-tenant).
{% endstep %}
{% endstepper %}

<figure><img src="https://2365162339-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FiqBD4M0nHFMaFeKR75p9%2Fuploads%2Fgit-blob-d6118868044df4c9fbc964f54bcce892b5f9f7d5%2Fdevice-form-new-pass-scanner-single-frame.png?alt=media" alt="New device form with the General, Profiles and Advanced settings cards"><figcaption><p>The New device form: name, description, profiles and advanced settings.</p></figcaption></figure>

{% hint style="info" %}
The connection QR code is only shown when it is issued. If it was not captured, or if it may have been seen by the wrong people, use **Reset connection** on the device (see [Reset a device connection](#reset-a-device-connection)).
{% endhint %}

A naming convention keeps the fleet readable, for example a store code, a gate number or a role: `Paris-Opera-Counter-1`, `VIP-Gate-A`, `Cloakroom-2`.

### Share the connection QR code securely

The connection QR code is a credential: anyone who has it can connect a phone to the tenant. Share it only with the staff member or supervisor responsible for that phone. The safest approach is to display it on the administrator's screen while the operator sets up the phone, rather than sending it through email, chat or screenshots. Once forwarded, access is no longer controlled by possession of the phone alone. When in doubt, reset the connection.

### Assign profiles

A device runs one profile at a time. When several profiles are assigned, staff pick one in the app, which starts a session. Assigning, removing or reordering profiles is done in the **Profiles** card of the device. Connected phones pick up the change within seconds, others when back online.

### Follow sessions and logs

Each device has a history of its activity, useful to check which profile ran where and to troubleshoot a phone in the field.

| View                                          | Content                                                                                                                                                                                                                                |
| --------------------------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| **Last connection** and **Total connections** | When the phone last connected, and how many times it connected.                                                                                                                                                                        |
| **Sessions**                                  | Each session with its start, end, profile, duration and end reason: closed on the device, another profile started, closed from the admin console, or profile schedule ended. The running session can be closed from the admin console. |
| **Logs**                                      | What the device reported, and what the platform logged on its behalf, in device time. Logs and ended sessions can take up to 5 minutes to appear.                                                                                      |

The **Telemetry** settings, under **Advanced settings**, control how much the phone reports: the minimum severity (Verbose, Information, Warning, Error or Critical; Information by default) and the upload interval, from 5 to 3,600 seconds, 60 by default. Raise the minimum severity to reduce noise; lower it temporarily to Verbose to investigate an issue.

### Deactivate, activate or delete a device

| Action         | When                                                                                                                                      | Effect                                                                               |
| -------------- | ----------------------------------------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------ |
| **Deactivate** | Access should stop temporarily: seasonal operations, temporary staff, a lost phone that may be recovered, or a short-term security doubt. | A deactivated device is refused when it connects, and its running session is closed. |
| **Activate**   | A previously deactivated phone is authorized to return to service.                                                                        | The device can connect again.                                                        |
| **Delete**     | The device will not come back, for example after a permanent decommissioning.                                                             | Its credential is revoked and its session is closed.                                 |

If a device may return later, deactivating is safer than deleting.

### Reset a device connection

**Reset connection** rotates the credential of an existing device. It ends the current connection and sign-in, makes every existing QR code for the device invalid, and issues a new one for the same device, with the same profiles and history. It is the fastest way to restore trust when the QR code may have been exposed, when the phone is replaced, or when setup must be done again under controlled conditions.

## Operational recommendations

Treat each credential as high-trust information:

* Use names that identify the location or role clearly.
* Assign only the profiles the phone needs.
* Deactivate unused devices as soon as a shift, event or campaign ends, and reset the connection immediately if a QR code was shared too broadly.

## FAQ

<details>

<summary><strong>Why is the Devices page unavailable?</strong></summary>

Devices may not be enabled on the tenant. Contact The Wallet Crew support to have the feature enabled.

</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 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/manage-devices.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.
