> ## Documentation Index
> Fetch the complete documentation index at: https://docs.truu.ai/llms.txt
> Use this file to discover all available pages before exploring further.

# Shared devices

> Verify frontline staff who work at shared workstations, such as a retail floor PC, a clinic workstation or a front desk, using the Shared Devices template and the right delivery pattern.

This page is for the administrator covering frontline staff who share computers. When you finish you will know which flow to start from, how to get a verification to someone who doesn't own the device in front of them, and how to lock down the shared browser.

Verification on a shared device works the same as everywhere else: something starts a request, a use case picks the flow, and the employee completes it. What changes is the device: it isn't theirs, its camera may be poor, and the employee may or may not have a phone.

## Start from the Shared Devices template

In **Flows**, apply the **Shared Devices** template (in the first-run tour it's **Frontline staff**). It creates a flow with:

| Column | Factors | Notes |
| - | - | - |
| A | Face | Runs on the employee's phone through the QR handoff, or on the device's camera |
| B | Badge | The badge identifier is matched to a directory attribute |

Then route it: in **Use Cases**, add a rule that sends your frontline group to this flow for the use cases they use.

## Choose columns that fit the device

| Situation | Column to use |
| - | - |
| Staff carry a phone | Face, with Proofing as a fallback |
| Staff have a phone but a weak reference photo | Proofing, then Knowledge + Email |
| No phone, and the device has no usable camera | Knowledge + Email (the code arrives in the work mailbox, opened on the shared device) |
| No phone, and the device has a badge reader | Badge + Email |

> [!WARNING]
>
> Never use Knowledge or Badge alone in a column. Answers can be researched and badges can be borrowed; pair them with a one-time code at minimum.

Check coverage before relying on these: badge or employee ID coverage in your directory's attribute mapping, and whether staff can reach their mailbox from the shared device. See [Connect your directory](https://docs.truu.ai/idv/connect/directory/overview.md).

## Getting the link to the employee

* **Self-service at the shared device.** Open the [self-service portal](https://docs.truu.ai/idv/use-cases/credential-reset.md#self-service-portal) in the shared browser. The employee enters their work email and receives the link on their own phone, so the shared device never needs a camera.
* **Your own sign-in or badge-in system.** Your system calls the API to create a link and shows it as a QR code; the employee verifies on their phone and your system reads the outcome. See [API quickstart](https://docs.truu.ai/idv/api/quickstart.md).
* **Device enrollment on a shared Windows PC.** The enrollment agent shows the verification and hands camera steps to the phone. See [Verified device enrollment](https://docs.truu.ai/idv/use-cases/device-enrollment.md).

## Lock down the shared browser

* Allow `https://verify.truu.ai` and `https://agent.truu.ai`. Add the proofing and face liveness hosts only if the device's own camera will be used. See [Network requirements](https://docs.truu.ai/idv/security/network.md).
* If the device camera will be used, pre-grant camera permission for `verify.truu.ai` by browser policy; staff usually can't answer the permission prompt.
* Exclude those hosts from TLS inspection.
* Clear browser state between sessions so the next person doesn't land in someone else's verification.

## What to tell staff

* Use your phone if you have one; the screen will show a code to scan.
* The page shows your company's name and never asks for a password.
* If you have no phone, you'll answer a question about your record and get a code at your work email.

## Related

* [Flows and templates](https://docs.truu.ai/idv/build/flows.md)
* [Badge](https://docs.truu.ai/idv/factors/badge.md)
* [Self-service credential reset](https://docs.truu.ai/idv/use-cases/credential-reset.md)


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.