> 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-web-app/accounts/protecting-your-accounts/save-the-backup-or-recovery-codes-of-your-account.md).

# Save the backup or recovery codes of your account

This article describes how to save in Cerby the backup or recovery codes of your account.

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

* Workspace **Owners**, **Super Admins**, **Admins**, and **Users**
* **Account Owners**
* Only supported using the Cerby web app
  {% endhint %}

As an account **Owner**, you can securely save in Cerby the backup or recovery codes of your accounts after turning on multi-factor authentication (MFA).

These single-use codes help you log in to your apps or recover access when your primary MFA method is unavailable. When supported by the app, Cerby recommends that you always save the backup or recovery codes, especially when Cerby manages MFA:

* You avoid using insecure and easy-to-lose storage methods, such as text files or physical notes.
* You can prevent business continuity risks, as other account **Owners** with shared access to the account can view the codes.
* Cerby encrypts these codes as it does with other sensitive data, and they are associated with the account, not an individual or a device.

{% hint style="info" %}
**NOTE:** Take the following into consideration when saving backup or recovery codes in Cerby:

* Not all apps support these codes.
* You can save the codes any time after turning on MFA; however, Cerby recommends that you do it right after completing the MFA setup.
* If your app only displays the codes in the mobile app, you must enter the codes manually in the Cerby web app.
  {% endhint %}

To save the backup or recovery codes of your account, you must complete the following steps:

1. Log in to your account through the app’s login page.
2. Navigate to the MFA page in your app settings.
3. Look for the backup or recovery codes option. Commonly, the apps display a list of single-use codes.
4. Copy the codes.
5. Log in to your [Cerby](https://app.cerby.com/) workspace in a separate browser tab.
6. Click the corresponding account card. The account details page is displayed with the **Settings** tab activated.
7. Expand the **Emergency controls** section at the bottom of the account details page.
8. Click the **Add codes** button. The **Add MFA Backup Codes** dialog box is displayed.
9. Paste the codes in the **MFA Backup Codes** field.
10. Click the **Save Codes** button. The dialog box closes, and a success message is displayed.

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-web-app/accounts/protecting-your-accounts/save-the-backup-or-recovery-codes-of-your-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.