> For the complete documentation index, see [llms.txt](https://docs.stoik.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.stoik.io/onboarding/account/passkey.md).

# Sign in with a passkey

A passkey lets you sign in to Stoïk Protect using your device's biometrics (Face ID, Touch ID, or a hardware security key) instead of a password. Passkeys are phishing-resistant and faster than any code-based method.

You can use a passkey in two ways:

* Passwordless sign-in: tap your fingerprint or face and you're in. No password, no code.
* As a second factor: after entering your password, confirm with your passkey instead of a 6-digit code.

## Setting up a passkey

Open the menu in the lower-left corner of the app, then go to `User settings` > `Security`. In the `Passkeys` section, click **Manage**, then **Add a new device**. You may be asked to confirm your MFA again.

Your browser will prompt you to confirm using your device's authentication method (Face ID, Touch ID, Windows Hello, or a hardware key). Once confirmed, the passkey is saved and ready to use.

You can add multiple passkeys, for example, one on your laptop and one on your phone. Give each one a name so you can tell them apart.

## Signing in with a passkey

On the Stoïk Protect login page, click **Continue with a passkey**.

Your browser will ask you to confirm with your device. After confirming, you land straight in Stoïk Protect, no password needed.

If you have previously signed in with another method, a Last used badge shows on the button you used most recently.

## Using a passkey as a second factor

If your account has MFA enabled, your passkey can serve as the second factor after your password. After entering your email and password, choose Passkey when prompted for your second factor and confirm with your device.

## Managing your passkeys

From `User settings` > `Security` > `Passkeys`, you can:

* Rename a passkey
* Remove a passkey you no longer use

If you remove all passkeys, you will need another sign-in method (password, Google, or Microsoft) to access your account.

## Troubleshooting

<details>

<summary>The passkey prompt doesn't appear</summary>

Make sure you're using a supported browser (Chrome, Safari, Firefox, Edge). The Stoïk desktop app may not support passkeys. Use the browser instead.

</details>

<details>

<summary>"No passkey found for this account"</summary>

You may be on a different device or browser than where you registered the passkey. Try your other devices, or sign in with another method.

</details>

<details>

<summary>You lost the device your passkey was stored on</summary>

Sign in with your password, Google, or Microsoft account. Then go to `User settings` > `Security` > `Passkeys` and remove the lost passkey.

</details>

<details>

<summary>You want to add a passkey from a password manager (1Password, Bitwarden…)</summary>

When your browser shows the passkey prompt, choose your password manager as the storage location.

</details>


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.stoik.io/onboarding/account/passkey.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.