> For the complete documentation index, see [llms.txt](https://docs.documint.me/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.documint.me/introduction/basic-tutorials/enable-multi-factor-authentication-mfa.md).
# Enable Multi-Factor Authentication (MFA)
If your business requires **Multi-Factor Authentication (MFA)**, you can enable it from your account settings.
{% stepper %}
{% step %}
### Open your account settings
Go to **Account Settings** and locate the **Security** section. Click **Enable MFA** and enter your account password to begin the setup.
{% endstep %}
{% step %}
### Connect your authenticator app
Scan the **QR code** using your preferred authenticator app. Then, enter the **6-digit verification code** generated by the app.
If you can't scan the QR code, **click the option** below it to display a setup key. Copy the key and enter it manually into your authenticator app.
In the app, add the required information, save it, and enter the **6-digit verification code** generated by the app.
{% endstep %}
{% step %}
### Save your backup codes
Once MFA is enabled, you'll receive **10 backup codes**. Make sure to store these codes somewhere safe. You'll need them to access your account if you can't use your authenticator app.
Once it's stored, check the box confirming that the backup codes are stored and click **Done**.
{% endstep %}
{% step %}
### You're all set! :tada:
That's it! **Multi-Factor Authentication is now enabled** on your account.
{% endstep %}
{% endstepper %}
---
# 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.documint.me/introduction/basic-tutorials/enable-multi-factor-authentication-mfa.md?ask=&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.
