Passkeys

Let customers sign in with a passkey.

Customers use a passkey they have enrolled, with a device unlock or a compatible authenticator. Workspace access still follows the permissions on their account.

Local browser test Enrollment verified

Test passkey

  • AccountSynthetic test account
  • AuthenticatorVirtual WebAuthn device
  • VerificationDevice confirmation required
Sensitive actions

Confirm your identity

  1. Request a changeInvite a workspace member
  2. Verify the accountMatch the signed-in account
  3. Complete the changeWithin 5 minutes of verification

From enrollment to sign-in

The local build uses Keycloak WebAuthn. Browser tests confirmed enrollment and sign-in with a virtual authenticator.

  1. Enroll on an account

    After establishing the account, the user enrolls a passkey from the hosted authentication flow.

  2. Confirm with the authenticator

    The browser asks the authenticator to prove possession of the enrolled credential. Covenant uses the verified identity to start the session.

  3. Confirm sensitive changes

    For invitations and access changes, the console checks that the same account verified its identity recently.

Plan for account recovery

Before a production pilot, test enrollment across the supported devices and confirm that the deployed authentication policy requires the right factor for privileged actions. Recovery needs its own verified flow for people who lose a device or passkey.