TL;DR: Shared ward devices make passkey governance harder when shared Windows accounts and pooled workstations blur ownership, according to Crayonic. Identity controls need attribution, revocation and session separation to fit communal clinical use.
Editorial analysis by NHI Mgmt Group, based on content published by Crayonic: “A passkey belongs to one person. A ward computer belongs to everyone.”.
Key questions
Q: Why do synced passkeys create governance problems for corporate accounts?
A: Synced passkeys can escape the organisation’s control when they land in a personal cloud account that IT cannot inspect or revoke.
Q: What signs show passwordless controls are being used in the wrong context?
A: Watch for shared Windows accounts, multiple staff using the same sign-in profile, unclear ownership of enrolled credentials, and policies that assume a device is personal when it is actually communal.
Q: How should teams deploy passkeys on shared workstations?
A: Use a shared-device policy, not a blanket passwordless policy.
Practitioner guidance
- Map passkey rollout by device ownership Classify endpoints as dedicated, shared, or kiosk-like before deciding where passkeys are acceptable and where they are not.
- Separate account lifecycle from device lifecycle Define who can enroll, revoke, and recover synced passkeys when the credential is attached to a cloud account rather than a local workstation.
- Prefer roaming authenticators for communal workstations Issue portable authenticators where many users share the same PC so the credential remains tied to the person, not the shared device.
Bottom line: Passkeys do not remove the need to model who owns the device, account, and session in a shared environment.
Glossary terms: Passkey, Synced Passkey, Roaming Authenticator, Shared Device Mode
Explore further
View Full Forum → | NHI Foundation Course → | Our Services → | Read the full analysis →
Shared-device passkey risk is a governance mismatch, not an authentication failure: passkeys are being asked to solve a problem they were not designed to own. The central issue is that hospital workflows often treat the workstation as communal while identity controls still assume a stable person-device pair. Practitioners should read this as a boundary problem between authentication and operational access design.
A few things that frame the scale:
- 92% of organisations expose NHIs to third parties, raising concerns about supply chain security, according to the Ultimate Guide to NHIs.
A question worth separating out:
Q: What should identity teams do when a passkey programme reaches frontline devices?
A: Reassess whether the device is dedicated, shared, or pooled, then align the credential type to that model. If the device is shared, treat the rollout as a governance decision about enrollment, recovery, revocation, and session handoff, not just a sign-in feature choice.
👉 Read our full editorial: Passkeys break down on shared ward devices and shared accounts