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:
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
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.
Getting the link to the employee
- Self-service at the shared device. Open the 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.
- Device enrollment on a shared Windows PC. The enrollment agent shows the verification and hands camera steps to the phone. See Verified device enrollment.
Lock down the shared browser
- Allow
https://verify.truu.aiandhttps://agent.truu.ai. Add the proofing and face liveness hosts only if the device’s own camera will be used. See Network requirements. - If the device camera will be used, pre-grant camera permission for
verify.truu.aiby 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.

