Access Flow

Physical Access Self-Service Platform — Product Spec v0.3

Access Flow governs. Your Physical Security Access Control System enforces.

Version 0.3 · updated 22 Nov 2026

Spec for a self-service and governance layer over existing access control systems (Physical Security Access Control Systems) for multi-site enterprises. v0.3 records the decisions since v0.2: customer-configurable security levels, guest invite or link per guest, 30-minute magic links, NOX/SIMS as the first integration via its SQL integration table at no extra licence cost, PIN reveal with safeguards, mandatory sponsor and dates, card activation by manager or sponsor, no approval timeouts, duration and renewal defaults, an area owner overview with revocation, end dates written to the Physical Security Access Control System and reconciliation in the prototype, revocation alerts and emergency revoke, theme-proof map meaning, and passkey (WebAuthn/FIDO2) sign-in as an optional alternative and fallback to SSO, as the sole sign-in method at fully offline sites, and with guest enrolment via magic link (22 Nov 2026, decided by Kim).

1. Scope, delivery and requirements

First customers
Multi-site enterprises (SMB is a later goal)
Hardware
Integrate existing Physical Security Access Control Systems and controllers; no own hardware
Problem addressed
Weak self-service and weak integration in current systems
Immediate delivery
Front-end UX prototype; security staff fulfil requests manually, including end dates, and reconcile against Physical Security Access Control System report data (no live Physical Security Access Control System integration)
First integration
NOX/SIMS, after the prototype
Deployment models
SaaS cloud managed by us (focus), customer-hosted hybrid in the customer's cloud, isolated in the customer's datacenter; none built yet
Prototype status
In progress, not completed (cloud build running as of 8 Nov 2026)

Product requirements

The product requirements list now lives on its own page. It was moved there once and the pages are not synced.

Design mockups

Design concepts; may not reflect the latest specification.

Deployment models

ModelHosted byPriority
1. SaaS cloud solutionManaged by usFocus
2. Hybrid solutionThe customer, in their cloudSupported later
3. Isolated solutionThe customer, in their own datacenterSupported later

All three models should be possible, and the focus is on the first. These are planned product deployment options; none has been built or provisioned, and the prototype stays a front-end with manual fulfillment.

SaaS tenancy: customers share one SaaS application, and each customer has its own separate database. This does not mean separate application instances per customer, and the database engine, servers, keys, backups and credentials are not specified here. Tenant isolation still applies throughout, including sites, areas and roles.

SaaS connector: a connector runs inside the customer's network. It only opens outbound encrypted connections to the SaaS service, so the SaaS service needs no inbound connection into the customer's network, and it reaches the SIMS database integration table locally, so that database is not exposed publicly. Protocol and connection details are not specified here.

Isolated deployment: runs without internet or SaaS connectivity. Core operation never depends on online SaaS callbacks, telemetry, online activation or online updates; updates are delivered offline and applied under the customer's control. Any dependency in that model, such as identity and SSO, must also work within this offline requirement; how is still to be designed.

Not yet decided: the cloud provider, and commercial terms and operational responsibilities for the customer-hosted models.

Anything in this spec that isn't on the Product requirements page is a proposal.

2. Identity, SSO, roles and scoping

ConcernDecision
AuthenticationPasskeys (WebAuthn/FIDO2) as an optional alternative and fallback to enterprise SSO via SAML 2.0 or OpenID Connect; a user can sign in with either, except at a fully offline site, where passkeys are the only sign-in method
Identity authorityEntra ID or Workday, configured per tenant; source of people and employment dates
Local identitiesExternal Employees and temporary visitors may exist only in the platform; sponsor, start and end required
Guests (Entra ID tenants)Sign in via Entra ID guest accounts; for each guest, either invite a new guest account or link an existing one
Guests (other tenants)Sign in via an email magic link to their local record; link and session last 30 minutes

Authentication answers who is signed in; the identity authority answers who is employed and until when. A tenant can use one system for both or different ones; choosing Workday as the identity source does not decide which SSO is used. A local external employee or visitor does not need to exist in the HR or identity source first.

Magic links and the sessions they start last 30 minutes. Proposed: links are single-use and valid only for the guest's own local record. In the prototype the flow is simulated, with no real emails or credentials.

Passkey sign-in

Decided (22 Nov 2026, Kim): passkeys (WebAuthn/FIDO2) are an optional alternative and fallback to the tenant's SSO/IdP. A user can sign in with either method. Passkeys do not replace SSO and are not the preferred or primary sign-in method. Enterprise SSO via SAML 2.0 or OpenID Connect stays available for enterprise tenants, and guest magic links stay as specified above.

Decided (22 Nov 2026, Kim): at a fully offline site (no internet, so the tenant's SSO/IdP is unreachable), passkeys are the only sign-in method, because they can be verified locally. Passkeys authenticate only to the Access Flow portal, not to doors; the Physical Security Access Control System keeps enforcing door access locally.

Decided (22 Nov 2026, Kim): guests enrol a passkey via a magic link (an emailed one-time link). The lifetime of that enrolment link is not yet decided.

Proposed: a user enrolls a passkey after their first sign-in via SSO. A user can register more than one passkey. Both synced passkeys (for example those held in a platform authenticator such as iCloud Keychain or Google Password Manager) and device-bound passkeys are supported.

Decided (22 Nov 2026, Kim): passkeys are a fallback and are not required. They are optional for users. Tenants cannot require passkeys, and SSO is not disabled in favour of passkeys, except at a fully offline site, where passkeys are the only working sign-in method as already recorded.

Decided (22 Nov 2026, Kim): recovery fallback is admin intervention. A tenant admin restores access or allows re-enrolment when a user loses their passkey. Those admin recovery actions are written to the audit trail (who, for whom, when).

Not yet decided: whether the prototype simulates passkeys or only documents them for a later phase. Proposed: production passkey support is part of phase 2; the prototype may simulate enrolment and sign-in, with no real authenticator required.

A valid signed-in session, started with SSO or a passkey, is what later sections mean when they require a valid SSO session, unless a later rule names a specific method.

Sponsor, start date and end date are mandatory for every external employee and visitor; a record missing any of them is rejected. Managers can onboard external employees.

Duration and renewal defaults

SettingDefault
Maximum sponsorship1 year
Visitor duration7 days
Renewal default: employees5 years
Renewal default: external employees1 year
Renewal default: guests30 days

Every value is configurable per customer; these are the defaults. The 7-day visitor duration limits a visitor's initial validity, and the 30-day guest renewal default is a separate setting; one does not change the other.

Renewals are never granted automatically and never bypass approval; existing approval rules apply. A renewal can't carry access past the person's eligibility end; that needs a separate, authorised change to employment or sponsorship dates.

Each renewal default is both the review interval and the length of each extension. Reaching the review interval starts the renewal workflow; it does not grant or extend access by itself, and the extension still follows normal approval and stays within eligibility.

Roles

RoleScopeCan doCannot do by default
EmployeeSelfView map, request access, upload photo, activate own card, set PINApprove anything
ManagerTeamRequest for team, set team members' escalation and delegation paths (later phase), onboard external employees, activate cards of external employees they manage, approve where the level assigns managersApprove where the level assigns only area owners
External Employee / visitor / guestSelf, within sponsorshipRequest access, upload photo, set PIN, time-limitedActivate own card or extend own sponsorship
SponsorSponsored peopleSet and end sponsorship dates, request access and activate cards for themActivate cards of people they don't sponsor; exceed policy maximum duration
Tenant adminOne tenantManage people, sites, theme, security levels and settings; set users' escalation and delegation paths (later phase); receive alerts for unconfirmed revocationsApprove area access just by being admin
Area ownerAreas they ownApprove requests, view the overview of their areas, revoke access in their areas, run access reviewsRevoke in areas they don't own; disable a person tenant-wide; administer people or settings
Security staffTenant or sitesConfirm or fail manual fulfillment, including end dates and revocations; emergency revoke; reveal a PIN for their task; work on reconciliation findings; receive alerts for unconfirmed revocationsApprove requests just by being security staff; reveal PINs outside their assigned task

Proposed rules: approval rights are separate from administration, each role assignment is a role plus a scope, and nobody can approve their own request. Security staff do the manual fulfillment in the prototype, and the role stays in production after NOX/SIMS integration for exceptions and oversight. Proposed: routine fulfillment is automated where the connector supports it, while security staff handle exceptions, emergency and other manual work, and oversee reconciliation; this does not mean every production change needs manual approval.

3. Core domain model

Tenanttheme, SSO, passkeys, identity, security levels
Site / floormap geometry
Areasecurity level, owner(s)
Door / reader
Personauthoritative or local; guest link
Eligibilityemployment or sponsorship dates
Credentialcard, PIN, photo
Entitlementperson × area, start/end, approvals
Fulfillment recorddesired vs confirmed

Relationships: Tenant → Site / floor → Area → Door / reader. Person → Eligibility and Person → Credential. Eligibility → Entitlement (bounds). Area → Entitlement. Entitlement → Fulfillment record.

Person

Source is the identity authority (Entra ID or Workday) or local (external employee, visitor, with mandatory sponsor and dates). Guests are linked to an invited or existing Entra ID guest account where the tenant uses Entra ID, or sign in by email magic link otherwise.

Eligibility

Start and end date-time with time zone. The outer limit for every entitlement.

Credential

Card (assigned, activation pending, active, deactivated, revoked), PIN (secret, masked by default), photo. Card state is independent of entitlements: changing it never creates, broadens or removes area access.

Security level

Defined per tenant: name, and approver set to manager, area owner, or both.

Area

A zone drawn on the site/floor map, made up of doors, with one security level and one or more owners; later mapped to access levels in each Physical Security Access Control System.

Entitlement

A person's approved access to an area, with an end no later than their eligibility end. Keeps every approval step (approver and time) and, if revoked, the confirmed revocation record: actor, time and reason. The original grant and approvals are never overwritten. Entitlements are independent of card state and stay in place when a card is deactivated.

Fulfillment record

Desired vs confirmed state, including the person, card, areas and start/end dates entered in the Physical Security Access Control System, plus who confirmed it and when (manual in the prototype, adapter later). Used for grants, revocations and emergency revocations.

Reconciliation report

A monthly comparison of Physical Security Access Control System records against the platform, with data captured-at and compared-at times, coverage (sites, areas, record types) and findings; each finding links to a remediation task. In the prototype it uses imported or mock Physical Security Access Control System report data (see section 5).

Rule: an entitlement's effective end is the earlier of its own end date and the person's eligibility end. Shortening eligibility shortens every entitlement.

4. Access map, requests and approval

Map stateMeaningShown as
Has accessFulfillment confirmed, and now within the validity window and eligibilityGreen plus label and icon
No accessNo entitlementRed plus label and icon
PendingRequested, or approved but fulfillment not yet confirmedDistinct style plus label
UnknownState cannot be determinedDistinct neutral style plus label

Every signed-in user sees the full map of their own tenant, whatever access they have. Clicking an area opens a request for it. Seeing an area never grants access or skips approval. State is never shown by color alone.

The labels and icons for has access, no access, pending and unknown stay the same under every tenant theme; a theme can change colors but not this meaning.

Green only when fulfillment is confirmed, so approved but unfulfilled access shows as pending, even when every approval step is complete. Approval and fulfillment are separate states.

Green also requires the current time to be within the access start and end and the person's eligibility; access that has expired or not yet started is never green. In the prototype, confirmed means attested by security staff, not verified by the Physical Security Access Control System.

The map shows access assignment, not card status. Where a person has confirmed access but their card is not active, the area stays green with a separate inactive-card note, so the map never implies the card currently opens the door. Proposed wording for the note: "assigned access; card inactive".

  1. Request

    Click an area on the map; set dates and justification (self, team member or sponsored person).

  2. Policy check

    Eligibility, end date within the outer limit, required credentials present.

  3. Route

    To the manager, the area owner or both, as the tenant's security level for that area defines.

  4. Approve or reject

    Decision and reason recorded. Requests never time out or expire while waiting.

  5. Fulfil

    Prototype: security staff enter it in the Physical Security Access Control System with its start and end dates and confirm. Later: adapter.

  6. Confirm

    Map and requester update only after confirmation.

Security level matrix

Each customer (tenant) configures its own matrix: how many levels, their names, and whether each level is approved by the manager, the area owner, or both. Production values are set per customer, not fixed for all.

LevelPrototype approval chain
LowManager
MediumArea owner
HighManager, then area owner
RestrictedManager, then area owner, with a shorter maximum duration

Status: this suggested matrix is accepted for the prototype only. The v0.1 auto-approval option for Low is not part of it.

Timeouts, escalation and delegation

No approval timeouts

A pending request is never approved, rejected or expired automatically because nobody acted on it. This is separate from eligibility and access end dates, which still apply.

Escalation (production)

A requester can escalate a pending request immediately, without waiting. Escalation draws attention to the request; it never approves it or skips a required approver.

Delegation (production)

Approvers can delegate their approval authority. A delegate approves only within the delegating approver's scope.

Paths per user (later phase)

Escalation and delegation paths can be set on a user level. By default, both go to the employee's manager. The default only decides who receives an escalation or delegation; it never approves a request on its own, removes an area owner step the security level requires, or lets anyone approve their own request.

Delegation duration and path setting (later phase)

A delegation can last until the delegating employee's termination. A user's escalation and delegation paths can be set or changed by the user, the user's manager, or an administrator. There are no limits on who can be chosen as a delegate. Tenant isolation, the delegating approver's scope, required approval steps and the no-self-approval rule still apply to every request.

Prototype scope

Neither escalation nor delegation is part of the prototype; both are later-phase requirements.

Area owner overview and revocation

Area owners get an overview of all the areas they own, showing who has access, who approved it and when, and they can revoke access. Planned for the prototype scope; not built yet.

Overview showsDetail
AreasEvery area the owner owns, across sites
PersonName and type: employee, external employee, visitor or guest
StateActive (confirmed), pending (approved, not yet confirmed), revocation pending, revoked, expired
ValidityStart and end, capped by eligibility
ApprovalsEach approval step with approver and time; both steps where the route has two
FulfillmentWho confirmed it and when, shown separately from approval times
  1. Revoke

    The area owner revokes a person's access to one of their own areas. No further approval is needed.

  2. Record

    The actor, time and reason are recorded.

  3. Revocation pending

    Prototype: shown as pending until security staff update the Physical Security Access Control System and confirm; while unconfirmed it alerts security staff and tenant admins.

  4. Confirmed or failed

    A confirmed revocation ends the access; a failed one stays visible to the owner and security staff.

Scope: an area owner can revoke only in areas they own, never in other areas and never by disabling a person tenant-wide. In production the server enforces this. After a revocation, the original grant, its approvers and approval times stay in the history and audit trail.

Proposed UX: filters by area, by person and by state.

5. Lifecycle, fulfillment and provisioning state

StateMeaning
DesiredPlatform has decided the change
PendingAwaiting security staff (prototype) or adapter acknowledgment
ConfirmedRecorded as applied, with who and when (prototype: security staff attestation, not Physical Security Access Control System verification); the only state that can show green on the map
FailedCould not be applied; needs follow-up
DriftA reconciliation found a difference between the Physical Security Access Control System and the platform

Manual fulfillment (prototype)

Who

Security staff signed in with valid SSO.

What they enter

The correct person, card, areas and start and end dates in the Physical Security Access Control System, so time-limited access expires there on schedule.

Record

Each confirmation records the staff member's identity and an automatic timestamp. In production the server's clock is authoritative.

Meaning

A person's statement that the change was applied; reconciliation checks it against the Physical Security Access Control System.

Scope

Grants, card activations, revocations and emergency revocations, including those started by area owners.

PIN

Masked by default; authorised security staff can press Show PIN code to read it while entering it into the access system, and it re-masks automatically (see section 6).

Card activation

Employees activate only their own assigned card, and the only check is a valid SSO session. Guests, visitors and external employees cannot activate their own card. Their manager or sponsor activates it for them, with a valid SSO session, and only for people they manage or sponsor, not for anyone else in the tenant. Where an external employee has both a manager and a sponsor, either one may activate the card alone; it is not a dual approval. No extra identity check or approval is needed.

Card activation and area access are separate processes. Activation does not create or broaden entitlements; it enables the card for the access already assigned, approved and confirmed for that person, so no extra area approval is needed. Entitlements still end at their own end date or eligibility end, whichever is earlier.

A person can have assigned, approved access while their card is deactivated; deactivating a card doesn't revoke or delete any entitlement. Activation stays pending until security staff confirm it, separately from fulfillment of the person's area access.

Scheduled expiry and monthly reconciliation

Most Physical Security Access Control Systems support time-limited access, so access entered with its end date expires in the Physical Security Access Control System on schedule. When security staff enter changes correctly, the Physical Security Access Control System stays in sync, and a monthly report from the Physical Security Access Control System confirms it.

For the prototype: end dates are written into the Physical Security Access Control System by security staff as part of manual fulfillment, and the prototype includes reconciliation of actual Physical Security Access Control System state against desired state, using imported or mock Physical Security Access Control System report data. Automated connector writes come later.

Operating note: scheduled expiry is enforced by the Physical Security Access Control System where the access is time-limited there. An early or manual revocation, such as by an area owner, takes effect once the Physical Security Access Control System is updated. A reconciliation shows alignment at the time its data was taken, within what it covers.

Report findingExample
Missing in Physical Security Access Control SystemConfirmed in the platform, not found in the Physical Security Access Control System
Extra in Physical Security Access Control SystemFound in the Physical Security Access Control System, with no matching approved access in the platform
MismatchPerson, card, area or dates differ between the two
Expired still presentPast its end date in the platform but still active in the Physical Security Access Control System

An expired record kept in the Physical Security Access Control System as inactive or as history is not a finding; "expired still present" means it is still active there after its end date.

Report details

Each report records when the Physical Security Access Control System data was captured and when the comparison was run, and lists exactly which sites, areas and record types it covers. It says 'in sync' only for records it actually compared and found matching; anything outside its coverage is not reported as in sync.

Remediation

Every finding becomes a tracked task for security staff. The audit trail keeps who resolved it, when, and how it was resolved, including the action taken.

Later phase

The NOX/SIMS connector writes start and end dates directly, and reconciliation runs from connector data; NOX/SIMS supports both. Built after the prototype.

Termination

At the termination date and time, revoke access and deactivate credentials, and end any delegation the person granted; each change is tracked until confirmed.

Area owner revocation

Revokes one person's access to one owned area; tracked until confirmed like any other change.

Unconfirmed revocation alerts

Unconfirmed revocations stay visible and alert both security staff and tenant admins until confirmed or resolved.

Emergency revoke

Immediate manual revocation with the same confirmation tracking: pending until security staff update the Physical Security Access Control System and confirm.

6. Audit, PIN and photo privacy

Audit trail

Append-only log of requests, approvals, fulfillment confirmations, card activations, PIN reveals, passkey registration, passkey removal, passkey use, admin passkey recovery, revocations, emergency revocations, and reconciliation findings with how each was resolved: who, what, when, why. Every revocation records actor, time and reason, and never removes the original grant or its approvers. Passkey events record actor and time, never biometric data. Admin passkey recovery (restoring access or allowing re-enrolment) records who, for whom and when.

Access reviews

Area owners periodically recertify access; anything not recertified is removed.

PIN reveal

Masked everywhere by default. During manual fulfillment, authorised security staff can press Show PIN code. Each reveal is logged with actor and time, never the PIN value. PINs are never written to logs or audit exports.

PIN safeguards

The PIN re-masks automatically after 30 seconds. Only least-privilege security staff with valid SSO, scoped to the task, can reveal it. The prototype uses only an obviously fictitious demo PIN, and no real PIN is collected on any Page.

Photos

Validated for format and size; who can view them is restricted; retention after offboarding is set per tenant.

Data protection

Data minimisation and retention for EU customers (GDPR); exact obligations to be confirmed with legal counsel. For passkeys, the platform stores only WebAuthn public-key credentials and related metadata (for example credential id, display name and last used). Biometric data never leaves the user's device and is never stored, transmitted or processed by Access Flow.

Retention after offboarding

Photos and other personal data follow GDPR and standard HR practice. Within that, data is kept only for a lawful purpose and only as long as necessary, then deleted or anonymised. HR practice works inside GDPR, never overriding it. Retention and deletion rules are set per data category and per customer, based on that customer's lawful retention policy and obligations, not one fixed period for everything. Audit records follow their own retention rules: they are not kept identifiable indefinitely by default, and records a customer is required to keep are not erased automatically. The concrete periods are configuration and legal details to set per customer.

7. Enterprise theming

Each tenant can customize more than its logo: design tokens, typography, colors, component styling and terminology. The default is a neutral enterprise theme with no real company's branding.

Map meaning survives any theme. The labels and icons for has access, no access, pending and unknown are fixed, and contrast is checked when a tenant's colors are applied.

Proposed: the contrast check follows a recognised accessibility standard, with the exact level still to be chosen.

8. Integration: NOX/SIMS first (after prototype)

The first Physical Security Access Control System integration after the prototype is NOX/SIMS. The prototype itself stays manual with no live integration. Each Physical Security Access Control System gets an adapter behind one internal interface, and the platform offers only what an adapter supports.

NOX/SIMS supports writing start and end dates directly and providing data for reconciliation (record export).

SIMS supports integration by inserting data into a SQL integration table in its database, and this integration has no additional cost beyond the customer's existing SIMS licence. We have not tested this independently. This covers one integration path only; it does not imply arbitrary writes elsewhere in the database, other NOX APIs, or an SDK. The exact table and schema, supported payloads and operations, and credentials and permissions are implementation details to work out when building the connector. Capabilities in the table not marked as supported are still to be confirmed.

CapabilityWhy it matters
Create/update cardholderOnboarding, external employees, visitors
Assign/remove access levelsEntitlement fulfillment and revocation
Native start/end dates (supported)Scheduled expiry in the Physical Security Access Control System
Card activate/suspendActivation and termination
PIN writePIN management, replacing manual PIN reveal
Photo writePhoto upload
Data for reconciliation / record export (supported)Reconciliation and automated confirmation
Change eventsDetect changes made directly in the Physical Security Access Control System

NOX/SIMS validation tasks

TaskStatus
Integration path and licensing terms: SQL integration table; no cost beyond the existing SIMS licenceEstablished
Coverage of native start/end dates and record exportSupported
Obtain a test environmentPending
Map areas and security levels to NOX/SIMS access configurationPending

Only the items above are established. Other capabilities in the table (cardholder, access levels, card state, PIN, photo, change events) are not yet established through the integration table, and none of this has been tested by us. Integration table schema, payloads and database permissions remain implementation details.

9. Phased plan and acceptance tests

PhaseFocus
1 (in progress)Front-end prototype: SSO sign-in, themed tenant with contrast check, access map, request–approve–manual fulfillment for all roles using the suggested matrix, end dates written to the Physical Security Access Control System at fulfillment, reconciliation against imported or mock Physical Security Access Control System report data, unconfirmed revocation alerts, emergency revoke, area owner overview and revocation, card activation, PIN reveal with safeguards using a fictitious demo PIN, external employee/visitor onboarding, audit log
2 (proposed)Production hardening on the SaaS cloud model managed by us (the deployment focus): per-customer security level configuration, duration and renewal settings, approval escalation and delegation with per-user paths (default: the employee's manager), server-enforced area owner scope, monthly reconciliation on live customer Physical Security Access Control System reports, Entra ID / Workday identity sync, termination automation, guest invite or link, passkey (WebAuthn/FIDO2) sign-in, production PIN and photo handling, access reviews
3 (proposed)NOX/SIMS adapter via the SIMS SQL integration table, writing start and end dates directly and replacing manual fulfillment; reconciliation from connector data; security staff kept for exceptions and oversight
4 (proposed)More adapters, more tenants, cross-system reporting, and the customer-hosted hybrid and isolated deployment models

The phases set an order, not a schedule. Phase 1 simulates the backend; it does not connect to any live Physical Security Access Control System. No report, routine or live access has been generated, and none of the later items are built.

Acceptance tests (draft)

10. Open decisions

Decided (22 Nov 2026, Kim): passkeys are an optional alternative and fallback to SSO, not required, not the preferred or primary sign-in method, and do not replace SSO. A user can sign in with either the tenant's SSO/IdP or a passkey. Tenants cannot require passkeys, and SSO is not disabled in favour of passkeys, except at a fully offline site, where passkeys are the only working method. Guests enrol a passkey via a magic link (an emailed one-time link). Recovery fallback is admin intervention: a tenant admin restores access or allows re-enrolment when a user loses their passkey, and those actions are audit-logged (who, for whom, when). At a fully offline site (no internet, SSO/IdP unreachable), passkeys are the only sign-in method, because they can be verified locally. Passkeys authenticate only to the Access Flow portal, not to doors; the Physical Security Access Control System keeps enforcing door access locally.

  1. Cloud provider
  2. Commercial terms for customer-hosted deployments
  3. Operational responsibilities and terms for customer-hosted deployments
  4. Lifetime of the guest passkey enrolment magic link
  5. Offline sites require a locally running Access Flow instance or edge component to verify passkeys and sync back; the deployment model, and how passkeys, credentials and audit sync between site and cloud, are TBD
  6. Whether the prototype simulates passkey enrolment and sign-in, or leaves that to a later phase