# Manage devices The Devices page controls which phones are allowed to connect to Pass Scanner. Each device entry represents one scanner installation and one login credential. This page is where administrators create new devices, share the connection QR code, and revoke or rotate access when a phone changes hands. The device QR code should be treated like a password. Anyone with access to that QR code can sign in a device to Pass Scanner. Device management is therefore both an operational topic and a security topic. {% hint style="warning" %} The device QR code is a credential. It should only be shared through trusted channels and only with the staff member or supervisor responsible for that device. {% endhint %}
Real-world examples * **Event operations:** each gate supervisor receives a dedicated device QR code for a managed phone. * **Retail or lounge access:** each counter phone has its own device entry, which makes access easy to revoke without affecting the rest of the team. * **Temporary staff:** a device can be enabled for a campaign or event day, then disabled immediately after the shift. * **Lost or replaced phone:** the connection can be reset to invalidate the previous QR code and issue a new one.
Devices list in The Wallet Crew admin console for Pass Scanner.

The Devices page centralizes device creation, status management, and connection rotation for Pass Scanner.

## How device management works Pass Scanner uses QR-code-based sign-in. When a device is created, The Wallet Crew generates a QR code linked to that device record. The phone scans that QR code from the Pass Scanner app to establish its connection. Using one device entry per physical phone is the safest model. It keeps revocation precise, makes audits easier, and avoids sharing one credential across several operators. It also helps operations teams identify which phone should be disabled or reset when an incident occurs. ### Add a new device Adding a device creates a new login credential for Pass Scanner. This should be done for each phone that will scan passes in production. {% stepper %} {% step %} #### Create the device entry From the Devices page, select **New** to create a device. {% endstep %} {% step %} #### Enter the device details Add a clear name. An optional description can be used to identify the location, team, or purpose of the phone. New devices are enabled by default. {% endstep %} {% step %} #### Save and capture the QR code Once the device is created, the connection QR code becomes available. That QR code is the credential used by the Pass Scanner app to sign in the phone. {% endstep %} {% endstepper %} Using a naming convention helps keep the fleet readable. For example, a Brand can use a store code, gate number, or role such as `Paris-Flagship-Checkout-1` or `VIP-Gate-A`.
Create device form in The Wallet Crew admin console.

Each scanner phone should have its own device entry with a name that clearly identifies where and how it is used.

### Share the device QR code securely The device QR code should be shared with care because it grants access to Pass Scanner. In many deployments, the safest approach is to display it locally to the operator during setup rather than sending it through broad internal channels. If the QR code is forwarded by email, chat, or screenshot, access is no longer controlled by possession of the phone alone. That increases the risk of unauthorized sign-in. When in doubt, reset the connection and issue a new QR code. The QR code can only be viewed when the device is created. This makes the initial setup moment important. It should be captured and transmitted through a trusted process.
Device QR code displayed after creating a Pass Scanner device.

The connection QR code should be handled as a secret and only shared with the person configuring the intended device.

### Disable, enable, or delete a device Device status changes allow administrators to control who can sign in without recreating the whole fleet. The right action depends on whether access should be paused, restored later, or removed permanently. **Disable a device** when access should stop temporarily. This is useful for seasonal operations, temporary staff, lost phones that may be recovered, or any short-term security doubt. A disabled device can be enabled again later. **Enable a device** when a previously disabled phone is authorized to return to service. **Delete a device** when it is no longer needed and should not come back, for example after a permanent decommissioning. If a device may return later, disabling is usually safer than deleting.
Actions available on a Pass Scanner device, including enable, disable, and delete.

Disabling is the standard way to suspend access without losing the device record. Deletion is better suited to permanent cleanup.

### Reset a device connection Resetting the connection rotates the credential for an existing device. A new QR code is generated and the old one stops working immediately. This action is useful when the QR code may have been exposed, when the phone is replaced, or when setup must be performed again under controlled conditions. Resetting the connection is often the fastest way to restore trust without deleting and recreating the device.
Reset connection action for a Pass Scanner device in the admin console.

Reset connection invalidates the previous QR code and issues a new one for the same device record.

### Operational recommendations Device management works best when each phone has its own clearly named record and each credential is treated as short-distribution, high-trust information. This keeps revocation targeted and avoids operational confusion during busy periods. For most projects, the following practices reduce support load and security risk: * Create one device per physical phone. * Use names that identify the location or role clearly. * Disable unused devices as soon as a shift, event, or campaign ends. * Reset the connection immediately if a QR code was shared too broadly. * Prefer disabling over deleting when the device may return to service. ## FAQ
Should several phones share the same device? No. One device per phone is the recommended model. It keeps access control precise and makes investigation or revocation much easier.
What happens after a connection reset? The previous QR code becomes invalid immediately. A new QR code replaces it for the same device record.
When should a device be disabled instead of deleted? Disable a device when access should stop temporarily or when the phone may return later. Delete a device only when it is no longer needed at all.
Why is the QR code considered sensitive? The QR code is the login credential for Pass Scanner. Anyone who receives it may be able to authenticate a device, so it should be handled with the same care as a password.
What is the best response if a QR code was shared in an unsafe channel? Reset the connection immediately. This invalidates the previous QR code and restores control with a newly generated credential.