Most passwordless designs assume one person, one device and one phone, and frontline work breaks all three assumptions. Shift workers in retail, logistics, manufacturing, healthcare and hospitality share tablets, handhelds, tills and nursing station PCs, often cannot carry personal phones on the floor, and change users many times an hour. The usual result is a shared generic account, a password written on the device, or a PIN that everyone knows. This guide sets out the authentication options that actually work for shared devices (security keys and badges, QR code with PIN, shared device modes, shared PC modes and guest sessions), how to choose between them, how to roll them out and how to make sure one worker's session never leaks into the next. It is for IAM engineers, endpoint teams and operations leaders responsible for frontline estates.
Key takeaways
- The goal is individual accountability without friction. Every action on a shared device should be attributable to a named person (NIST SP 800-53 IA-2(5)), and sign-in must take seconds, or workers will find a workaround.
- A portable authenticator beats a device-bound one. Credentials tied to one device, such as per-device Windows Hello enrolment, scale badly when hundreds of people share dozens of devices. A FIDO2 security key, smart badge or QR badge travels with the worker.
- Not every "passwordless" option is strong. QR code with PIN removes typing but Microsoft classifies it as single-factor; security keys are phishing-resistant. Match the method to what the device can reach.
- Sign-out is a security control. Shared device modes and guest sessions exist to clear one user's tokens and data before the next user; apps that do not participate break the model.
- Enrolment and lost-badge recovery decide success. Plan supervised enrolment with a time-limited bootstrap credential, a same-day replacement route and a short-lived fallback for forgotten badges.
Why frontline authentication is different
| Constraint | Typical frontline reality | Consequence for authentication |
|---|---|---|
| No personal phone | Phones banned on the floor, not issued, or workers refuse to use personal devices for work | Push approval, authenticator apps and SMS are unavailable or unfair |
| Many users per device | A handheld used by three shifts; a till used by ten people a day | Per-device enrolment and long sessions do not work |
| Frequent switching | Nurses and pickers sign in dozens of times per shift | Sign-in must take seconds or it is bypassed |
| Gloves, masks, noise | Cold stores, clean rooms, clinical areas | Biometrics and typing are unreliable; tap or scan works better |
| High turnover and seasonal staff | Large intake before peak periods | Enrolment must be fast and supervised; leavers must lose access the same day |
| Mixed device fleet | Android rugged devices, iPads, Windows kiosks, ChromeOS | No single method covers every platform |
The risk of getting this wrong is not abstract. Shared generic accounts remove accountability for refunds, prescriptions and stock adjustments, and passwords on sticky notes make T1078 Valid Accounts trivial for anyone walking past. See the Shared and Generic Accounts Governance Guide.
Authentication options compared
| Option | How the worker signs in | Strength | Best fit | Watch out for |
|---|---|---|---|---|
| FIDO2 security key (USB or NFC) | Tap or insert the key, enter a key PIN or touch | Phishing-resistant, device-bound passkey | Shared Windows PCs, browsers, NFC-capable mobiles | Key cost, loss, PIN resets; not usable over RDP or VDI without WebAuthn redirection |
| Smart card or PIV-style badge | Tap or insert badge, enter PIN | Strong (certificate-based) where PKI is mature | Healthcare, government, sites with existing badge PKI | Certificate lifecycle and reader estate. See the Smart Card and PIV/CAC Authentication Guide. |
| QR code badge plus PIN (Microsoft Entra) | Scan a printed QR code with the device camera, enter a numeric PIN | Single-factor according to Microsoft | Store and warehouse mobiles on site networks | Mobile only; badge can be photographed; pair with location-based Conditional Access |
| Proximity badge tap into a session manager | Tap badge on reader; vendor software switches session | Depends on the second factor and badge technology | Clinical workstations with fast user switching | Some older proximity cards can be cloned; require a PIN or second factor for sensitive actions |
| Shared device PIN or pattern only | Unlock the device, then a shared app account | Weak, no individual identity | Avoid except for genuinely anonymous kiosk use | No attribution; PIN known by everyone |
| Personal phone authenticator | Push or code on the worker's phone | Varies | Only where workers have and accept work phones | Equity, policy and union concerns; phones not allowed in many areas |
Device-bound passkeys on security keys are described by the FIDO Alliance as offering the highest assurance, and the FIDO Alliance explicitly notes that some users need a credential that works across shared, restricted or unusual environments. That is the frontline case. For background on passkey types, see the Passwordless and Passkeys Guide.
Platform features for shared devices
Microsoft Entra shared device mode (iOS, iPadOS, Android)
- What it does: one sign-in gives single sign-on across participating apps, and signing out of the device signs the user out of all of them, so the device is ready for the next worker.
- Setup: an MDM such as Intune pushes Microsoft Authenticator with shared device mode turned on; iOS also needs the Microsoft Enterprise SSO plug-in. Manual setup needs the Cloud Device Administrator role and suits pilots only.
- App participation: line-of-business apps must be built as single account public clients with MSAL and must clear the previous user's cached data when the account changes. Apps that do not support shared device mode get neither single sign-on nor single sign-out, which is where data leaks between users.
- Conditional Access: policies can target shared devices, for example requiring enrolment and compliance before sign-in.
Microsoft Entra QR code authentication
- Design: a QR code identifies the user and a numeric PIN of 8 to 20 digits (default 8) authenticates them. Standard codes last 1 to 395 days (default 365); temporary codes for a forgotten badge last up to 12 hours.
- Limits: iOS, iPadOS and Android only, not desktop apps or browsers; disabled by default; the user must have signed in once with an existing method first. Microsoft documents that lockout threshold, lockout duration and PIN complexity are not configurable in the current release, and that barcode scanners cannot read the code.
- Positioning: Microsoft describes it as single-factor and recommends Conditional Access requiring phishing-resistant authentication or MFA when users access resources from outside the workplace network.
Windows shared PCs with security keys
- Enable: in Intune, Use security keys for sign-in under Windows enrollment, Windows Hello for Business (new enrolments), or the custom OMA-URI
./Device/Vendor/MSFT/PassportForWork/SecurityKey/UseSecurityKeyForSigninset to 1 for existing devices. Hybrid joined devices can use the Group Policy Turn on security key sign-in. - Requirements: Entra joined (Windows 10 1909 or later) or hybrid joined (2004 or later with patched domain controllers). Windows 10 1903 shared PCs also need shared PC mode (
EnableSharedPCMode). - Not supported: on-premises-only domain joined devices, RDP, VDI and Citrix (unless WebAuthn redirection is used), Run as, and server sign-in. Many clinical and retail estates rely on VDI, so test this first.
ChromeOS and iPad
- ChromeOS managed guest sessions: no Google Account sign-in; when the session ends through sign-out, maximum session length or idle limit, local data is wiped. Suited to anonymous or app-level sign-in uses; sign-in to business apps then happens inside the session through the identity provider.
- Shared iPad: requires supervision, MDM and organisation-owned Managed Apple Accounts. Temporary (guest) sessions delete all data at sign-out. Apple's deployment guide also describes an authenticated guest mode that uses the identity provider for sign-in and removes the account and data at sign-out; check its availability for your iPadOS version.
Where the shared device itself must be locked down (kiosk mode, app allow-lists, USB control), see the Kiosk and Shared Device Security Guide.
Choosing the right approach
| Scenario | Recommended primary method | Fallback |
|---|---|---|
| Shared Windows PCs in offices, depots or nursing stations, no VDI | FIDO2 security key or smart badge with PIN | Temporary Access Pass issued by a supervisor for one shift |
| Shared Windows PCs delivered through VDI or Citrix | Smart card or badge with a VDI-aware session manager, or WebAuthn redirection tested end to end | Supervisor-issued temporary credential |
| Store or warehouse Android or iOS handhelds on site | Shared device mode plus QR badge and PIN, or NFC security key where apps support WebAuthn | Temporary QR code (up to 12 hours) |
| Workers who also access HR or payroll from home | A personal phishing-resistant credential (passkey on own device or a key) for off-site access | Supervised re-enrolment |
| Anonymous public kiosk | No user sign-in; guest session with data wipe | Not applicable |
| Small business with a handful of shared tablets | Platform guest session plus an individual passkey or app sign-in per worker | Manager reset |
Small versus large estates: small sites can run supervised enrolment by hand and use platform defaults. Large estates need MDM-driven provisioning, badge printing integrated with HR-driven joiner records, a key and badge inventory, and per-site Conditional Access. Cost per worker matters: security keys are an upfront hardware cost, while QR badges cost only printing but give weaker assurance.
Enrolment, lost badges and leavers
- Bootstrap: use a short-lived, ideally one-time bootstrap credential issued by a supervisor after an in-person identity check. In Entra, the Temporary Access Pass defaults to a one-hour lifetime with an 8-hour maximum and 8-character length; set one-time use where enrolment fits in 10 minutes, because a single-use pass must complete passwordless registration within that window.
- Register at the station: enrol security keys at a supervised enrolment point, not on the shop floor device. Entra requires MFA within the previous five minutes before a passkey registration.
- Restrict models: use Enforce attestation with Enforce key restrictions (an AAGUID allow list) so only issued key models can register. Attestation is enforced at registration only, so set it before rollout.
- Lost or forgotten badge: provide a same-shift fallback (a temporary QR code or a one-shift Temporary Access Pass) and revoke the lost credential immediately. Track how often fallbacks are used.
- Session limits after a temporary credential: sessions created with a Temporary Access Pass are not invalidated when it expires, so set Conditional Access sign-in frequency to end the shift session.
- Leavers: disable the account from the HR feed the same day and recover or revoke the key or badge. See the Identity Lifecycle Event Design Guide.
Session hygiene between users
Shared devices fail when the second user inherits the first user's session. Common vectors are cached tokens in apps that do not support shared device mode, browser cookies on a shared PC profile, and apps that keep the last user's data on screen.
- Single sign-out: prefer apps that participate in the platform's shared mode; for those that do not, shorten session lifetime and clear data on launch.
- Idle lock and session end: apply device lock (NIST SP 800-53 AC-11) and session termination (AC-12) with timeouts set per area, shorter for clinical and cash-handling devices.
- Browser state: on shared PCs use guest or ephemeral profiles, or shared PC mode account deletion, so cookies do not persist. Stolen or left-over cookies map to T1539 Steal Web Session Cookie.
- Keyloggers on kiosks: PINs typed on a compromised shared terminal can be captured (T1056.001 Keylogging); security keys with on-key PIN entry or touch reduce what a keylogger gains.
- Data protection: on mobile, use app protection policies with selective wipe so business data is removed when the user signs out.
How to implement
- Map the estate: list device types, operating systems, VDI use, apps and their support for shared device modes or WebAuthn, and whether workers have phones.
- Pick one method per device class: use the decision table above and document the fallback for each.
- Pilot one site: choose a site with supportive managers; run two to four weeks; time sign-in and measure failure and fallback rates.
- Prepare policy in report-only mode: build Conditional Access policies targeting shared devices in report-only first, then enforce for pilot groups.
- Enrol at speed: run enrolment events tied to shift briefings with pre-staged keys or printed badges and supervisor-issued bootstrap credentials.
- Retire the shared accounts: once individual sign-in works, disable the generic accounts and monitor for attempts to use them.
- Scale in rings: extend site by site; keep the old method available for one rota cycle per site as a rollback, with an owner and end date.
- Rollback plan: if sign-in failures spike, re-enable the previous method for that site only, keep logging, and fix the cause rather than reverting the estate.
For the wider passkey programme this fits into, see the Passkey Rollout Guide.
Detection and measurement
- Log: sign-in method per event, device ID, site, fallback use, failed PIN attempts, Temporary Access Pass and temporary QR issuance (who issued, for whom), and generic account sign-ins.
- Alert: a single badge or key used on two sites at once; repeated temporary credential issuance for the same worker; any sign-in to a retired shared account (T1078.001 Default Accounts style abuse); PIN guessing patterns (T1110.003 Password Spraying) across many users from one device.
| Metric | Target direction | Why it matters |
|---|---|---|
| Median time to sign in on shared devices | Seconds, stable or falling | Slow sign-in drives workarounds |
| Share of shared-device sign-ins by a named individual | Towards 100% | Accountability |
| Fallback credentials issued per 100 workers per week | Falling after pilot | Lost badges and enrolment gaps |
| Active generic accounts | Zero, except documented anonymous kiosks | Removal of shared credentials |
| Leaver credentials revoked on last day | 100% | Joiner-mover-leaver discipline |
| Apps on shared devices without single sign-out | Falling | Session leakage risk |
Framework mapping
| Framework | Reference | How it applies |
|---|---|---|
| NIST SP 800-53 Rev. 5 | IA-2(5) Individual Authentication with Group Authentication | Individuals authenticate before a shared device or group account is used |
| NIST SP 800-53 Rev. 5 | IA-2(2), IA-4, IA-5, AC-2 | MFA for non-privileged users, identifiers, authenticator lifecycle, account management |
| NIST SP 800-53 Rev. 5 | AC-11, AC-12 | Device lock and session termination between users |
| NIST CSF 2.0 | PR.AA-03, PR.AA-05, PR.PS-01 | Authentication, least privilege, configuration of shared devices |
| ISO/IEC 27001:2022 Annex A | A.5.16 Identity management, A.5.17 Authentication information, A.8.5 Secure authentication | Unique identities and secure authentication on shared equipment |
| MITRE ATT&CK v20 | T1078, T1078.001, T1110.003, T1056.001, T1539 | Behaviours the controls are meant to prevent |
Common failure patterns
- Individual sign-in on a generic account: the device unlocks with a personal badge, but the app behind it still runs as a shared store account, so attribution is lost anyway.
- Apps outside shared device mode: one line-of-business app keeps the last user's token, and the next worker acts as them.
- VDI discovered late: security keys piloted on local desktops, then found not to work over the virtual desktop the floor actually uses.
- Long-lived fallbacks: temporary passes or temporary QR codes issued for days instead of a shift, becoming the real credential.
- QR badges treated as strong: a photographed badge plus an observed PIN gives full access from anywhere when Conditional Access does not restrict location or device.
- No same-day leaver process: seasonal staff leave with working keys or badges because nobody collects or revokes them.
Practitioner checklist
- Inventory shared devices, operating systems, VDI use and app support for shared modes and WebAuthn.
- Choose a primary method and a time-limited fallback for each device class.
- Restrict registrations to issued key models with attestation and an AAGUID allow list.
- Use one-time, short-lived bootstrap credentials for supervised enrolment.
- Enable platform shared modes and require apps on shared devices to support single sign-out or clear data on user change.
- Set device lock, idle timeout and sign-in frequency per area.
- Restrict single-factor methods such as QR badges to managed devices on site networks.
- Retire generic accounts and alert on any further use.
- Revoke keys and badges from the HR leaver feed on the last day.
- Track sign-in time, fallback rate and named-user coverage monthly.
Standards and references
- NIST: SP 800-53 Rev. 5
- FIDO Alliance: Passkeys
- Microsoft Learn: Shared device mode overview
- Microsoft Learn: QR code authentication method
- Microsoft Learn: Passwordless security key sign-in to Windows
- Microsoft Learn: Temporary Access Pass
- Apple: Shared iPad overview
- Google: Managed guest sessions on ChromeOS devices
Related NHI Mgmt Group resources: Passkey Rollout Guide · Kiosk and Shared Device Security Guide · Shared and Generic Accounts Governance Guide · Passwordless and Passkeys Guide