Skip to main content
Passkeys let you sign in to ShingleAI without a password using your device’s biometrics (Touch ID, Face ID, Windows Hello) or a hardware security key. Passkeys are phishing-resistant and don’t require remembering or rotating a shared secret.

Prerequisites

  • A device or browser that supports WebAuthn (every current major browser does)
  • A signed-in ShingleAI account — passkeys are added to your existing account, not used to create one

Add a passkey

  1. Navigate to Settings > User > Security
  2. In the Passkeys card, click Add passkey
  3. Your browser prompts you to choose a device — phone biometric, platform authenticator (Touch ID / Windows Hello), or a security key
  4. Complete the device prompt
The new passkey appears in the list with an auto-generated name (Passkey #1, Passkey #2, etc.) and the date it was added. Add as many passkeys as you have devices — each one is registered to that specific device.
You can register passkeys even if your account uses email-and-password sign-in. Passkeys are an additional sign-in method, not a replacement.

Rename or delete a passkey

In the Passkeys card:
  • Click the pencil icon to rename a passkey (max 64 characters) — useful for distinguishing “Work laptop” from “Personal phone”
  • Click the trash icon to delete a passkey, then confirm
Deleted passkeys cannot be restored — register a new one if you need access from that device again.

Sign in with a passkey

On the sign-in page:
  • Conditional UI (autofill). If your browser supports it, your saved passkey appears as a sign-in option directly in the email field’s autofill menu — pick it, complete the device prompt, and you’re in
  • Manual button. Click Sign in with a passkey to invoke the device picker without typing your email
You can sign in with a passkey from any device that has one registered to your account.

Limitations

  • Last-used timestamp not yet tracked. The passkey list shows the date a passkey was added but not when it was last used to sign in
  • Per-device. Passkeys are bound to the device that created them and don’t sync across browsers unless you use a synced passkey provider (iCloud Keychain, Google Password Manager, 1Password, etc.)

Next steps

Two-factor authentication

Add an extra factor with TOTP and backup codes

API keys

Programmatic access for external integrations