> 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/two-factor-authentication.md).

# Two-factor authentication

Some actions ask you to confirm it's really you with a code before they go through:

* Adding, changing or removing a wallet
* Claiming rewards
* Registering, editing or deleting a station
* Changing your account details

By default the code is sent to your email. Setting up an authenticator app (like Google Authenticator) lets you use a code from your phone instead.

### Set up an authenticator app

1. Go to Settings, then the "Security" tab.
2. Click "Enable 2FA".
3. Choose "Authenticator App".
4. Scan the QR code with your authenticator app.
5. Enter the 6 digit code shown in the app.

You will see "Two-factor authentication updated successfully" and the status will change to "Enabled".

{% hint style="warning" %}
Once 2FA is on, [generate your recovery codes](https://docs.wingbits.com/general-help/account/recovery-codes.md) and store them somewhere safe. They are the only way back in if you lose your phone.
{% endhint %}

### When you are asked for a code

A "Multi-Factor Authentication" window will pop up. Choose "Email Authentication" to get a code by email, or "Authenticator App" to use the code from your app, then enter it.

You may be asked again if you come back to make another change later.

### Change your authenticator app

To move 2FA to a new phone or app, go to Settings, then "Security", click "Update 2FA" and follow the same steps.

If you no longer have your old phone, use a [recovery code](https://docs.wingbits.com/general-help/account/recovery-codes.md#reset-2fa-with-a-recovery-code) to reset 2FA first.


---

# 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/two-factor-authentication.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.
