> For the complete documentation index, see [llms.txt](https://help.cerby.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.cerby.com/cerby-browser-extension/accounts/passkeys/add-a-passkey-to-an-account.md).

# Add a passkey to an account

This article describes how to add a passkey to an account using the Cerby browser extension.

{% hint style="info" %}
**Who can use this feature?**

* Account **Owners**
* Supported using the **Cerby browser extension** and mobile app. For the mobile app instructions, read the article [Create a passkey for an account](https://help.cerby.com/cerby-mobile-app/accounts/protecting-your-accounts/passkeys/create-a-passkey-for-an-account).
  {% endhint %}

As an account **Owner**, you can add a passkey to an account directly from the Cerby browser extension. When you register a passkey on an app, the extension identifies the passkey creation flow and prompts you to save the passkey to the matching Cerby account, so the passkey is available the next time you log in with Cerby.

{% hint style="danger" %}
**IMPORTANT:** Only account **Owners** can add a passkey to an account. Account **Collaborators** can use an existing passkey to log in, but cannot add or replace one.
{% endhint %}

## Requirements

Passkeys are supported only for a subset of apps, listed in [Passkeys.directory](https://passkeys.directory/). A listed app's passkey support can still vary by platform. Amazon and X (Twitter), for example, support passkeys on both web and mobile, but TikTok currently supports passkeys only on its mobile app, not yet on its website. As a result, TikTok passkeys aren't yet available through the Cerby browser extension, only through the Cerby mobile app. If you have any issues with a supported app, contact the Cerby Support team at <support@cerby.com>.

## Add a passkey to an account

To add a passkey to an account, you must complete the following steps:

1. Log in to your workspace in the Cerby browser extension. For instructions, read the article [Log in to the Cerby browser extension](/cerby-browser-extension/installation/log-in-to-the-cerby-browser-extension.md).
2. Navigate to the account security or login settings of your app.
3. Start the passkey registration flow. The browser's passkey creation prompt is displayed.
4. Select the option to save the passkey with Cerby. The **Add passkey to your account** dialog box is displayed.
5. Select the account you want to add the passkey to.

   <div data-gb-custom-block data-tag="hint" data-style="info" class="hint hint-info"><p>When Cerby finds a single account that matches the app, the account is selected automatically and you can skip directly to the next step.</p></div>
6. Click **Add passkey**. Your device's biometric or security-key verification is activated.
7. Complete the verification as directed by your browser. Cerby displays a **Passkey added to your account** message, and the passkey is saved to the account.

When you open the account list in the Cerby browser extension, a **Passkey** chip is displayed on any account row that has a saved passkey.

{% hint style="warning" %}
**CAUTION:** If the account already has a passkey saved, the **Replace passkey?** dialog box is displayed instead of the dialog box in step 6. Click **Replace passkey** to continue. Replacing a passkey removes the existing passkey from all devices where it was saved.
{% endhint %}

Now you are done.


---

# 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://help.cerby.com/cerby-browser-extension/accounts/passkeys/add-a-passkey-to-an-account.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.