Passkey Authentication Service  ·  View 03 of 21  ·  People and journeys

Actors and Their Core Journeys

Eight parties, three of them machines, and the goal each would state in their own words.

Editable source SVG draw.io All views
The people signing in Everyday user 180 M accounts Goal — Sign in on my phone without remembering anything, and still get back in when I drop it in a lake. Core journeys Enrol a first passkey after a password login Sign in on a new device Get back in with no devices the expensive one Multi-device user 2.3 credentials average Goal — Add my work laptop's security key without being asked to set everything up again. Core journeys Add a second credential Revoke a lost device The people who run a tenant Tenant administrator 40 tenants Goal — Turn the password off without my support queue exploding on Monday morning. Core journeys Turn off the password Change an authentication policy Support agent 320 seats Goal — Prove this caller is who they say they are without becoming the account's real authenticator. Core journeys Run an assisted recovery On-call engineer 1 primary, 1 secondary Goal — Tell a ceremony-store blip apart from a tenant that mistyped its origin, before the pager escalates. Core journeys Triage a login incident Machines and standards Relying-party backend 40 integrated Goal — Hand me a verdict I can verify offline, and let me keep issuing my own sessions. Core journeys Exchange a verdict for a session Metadata ingest job daily, signature-checked Goal — Refuse an unsigned metadata update rather than accept a fresher one. Core journeys Refresh the metadata snapshot Authenticator platform or roaming Goal — Never hand the private key to anyone, this platform included. Core journeys Sign an assertion Refuse a duplicate credential Passkey Authentication Service — Actors and Their Core Journeys Person or role Journey / task External / third party Security / platform Eight parties, three of them machines. The authenticator is in the cast because the one secret that matters never leaves it. v 1.0 · owner Security & Identity Architecture · date 2026-10

Why these eight

  • The everyday user's goal contains the whole problem: convenience plus a credible answer to losing the device. The second half is where passwordless designs fail.
  • The support agent's goal is the one most often left out — proving a caller's identity without the support desk quietly becoming the account's strongest authenticator.
  • The authenticator is in the cast because its goal (never hand over the private key) is a constraint on the platform, not a feature of it.
  • The metadata ingest job appears as an actor because its goal is to refuse, and a job whose job is to refuse needs an owner.

Assumptions

  • 320 support seats across the tenant estate; assisted recovery is a minority route but the most expensive per case.
  • Average 2.3 credentials per user, which means a large minority still hold exactly one.
  • 40 relying-party backends integrated, each issuing its own sessions.

Risks

  • A tenant that treats the support desk as its primary recovery route caps every account's assurance at whatever an agent can verify over a phone.
  • The multi-device user is the easy case and tends to dominate design reviews; the single-credential user is the one who generates the incidents.