> For the complete documentation index, see [llms.txt](https://docs.wingbits.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.wingbits.com/general-help/account/recovery-codes.md).

# Recovery codes

Recovery codes let you reset two-factor authentication if you lose access to your authenticator app. Each code can only be used once.

### Generate your codes

1. Go to Settings, then the "Security" tab.
2. Click "Generate Recovery Codes" (or "Regenerate Recovery Codes" if you already have some).
3. Verify with a code if asked.
4. Click "Copy All Codes" and store them somewhere safe, like a password manager.
5. Click "I've Saved My Codes".

{% hint style="warning" %}
The codes are only shown once. Generating new codes replaces any old ones.
{% endhint %}

### Reset 2FA with a recovery code

1. Go to Settings, then the "Security" tab.
2. Click "Reset 2FA".
3. Enter one of your recovery codes and click "Redeem".

You will see "Recovery code verified. Two-factor authentication has been reset." You can now [set up 2FA again](https://docs.wingbits.com/general-help/account/two-factor-authentication.md#set-up-an-authenticator-app). That code is used up, so cross it off your list.

"Invalid recovery code." means the code is wrong or has already been used.

### "Recovery Codes No Longer Valid" banner

If you see this banner on your dashboard, your old codes no longer work. Click "Generate New Recovery Codes" and save the new set. "Remind Me Later" hides the banner for now.


---

# 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.wingbits.com/general-help/account/recovery-codes.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.
