> For the complete documentation index, see [llms.txt](https://docs.debricked.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.debricked.com/product/administration/settings/two-factor-authentication-2fa.md).

# Two-Factor Authentication (2FA)

Learn how to enable or disable two-factor authentication.

Two-factor authentication increases the security of your account by introducing a second authentication method.<br>

To manage 2FA:

1. Hover on your name at the bottom of the left-side menu.
2. Click **User settings.**
3. Under **Two Factor Authentication,** select or deselect one or more options by ticking the corresponding checkboxes.

### **Email authentication**

When this option is enabled, you will start receiving confirmation codes to your email upon login. From now on, every time you log in, you will be prompted to enter the code received in the emails.

### **Google authenticator**

When this option is enabled, you will be required to approve your logins using the *Google Authenticator* app. To enable this option:

1. Tick the corresponding checkbox under **Two Factor Authentication**. This will prompt a modal with a QR code to appear on your screen.
2. Open the **Google Authenticator** app on your phone and scan the QR code. This will generate a single use code.
3. Enter the code in the **Verification code** field in the tool and click **Verify**. From now on, every time you log in, you will be asked to enter the authentication code from your **Google Authenticator** mobile app.


---

# 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.debricked.com/product/administration/settings/two-factor-authentication-2fa.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.