> 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-mobile-app/accounts/protecting-your-accounts/passkeys/remove-a-passkey-from-an-account-in-an-app.md).

# Remove a passkey from an account in an app

This article describes how to remove a passkey from an account in an app.

To remove a passkey from an account in an app, you must complete the following general steps:

{% hint style="warning" %}
**IMPORTANT:** These steps provide a general guide for removing or disabling a passkey. Review the specific process for each app because it may vary. Cerby recommends verifying the app's support documentation or settings for precise instructions.
{% endhint %}

1. Log in to the app with the account you want to remove the passkey from.
2. Access the account login or security settings within the app.
3. Locate the passkey section in the settings.
4. Select the **Remove passkey** or **Disable passkey authentication** option.
5. Confirm the removal.
6. Test the login process to the account without a passkey.

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-mobile-app/accounts/protecting-your-accounts/passkeys/remove-a-passkey-from-an-account-in-an-app.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.
