> For the complete documentation index, see [llms.txt](https://knowledgebase.autorabit.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://knowledgebase.autorabit.com/product-guides/vault/getting-started/set-up-multifactor-authentication-in-vault.md).
# Setting Up Multi-Factor Authentication
## What is Multi-Factor Authentication?
**Multi-Factor Authentication (MFA)** is a security mechanism that requires two forms of identity verification before granting access:
* **First factor**: User credentials such as a username and password.
* **Second factor**: A one-time verification code generated by an authenticator app or provided via a security device.
Enforcing MFA significantly reduces the risk of unauthorized access to your AutoRABIT Vault data by requiring something the user **knows** and something the user **has**.
***
## Enabling MFA for Your AutoRABIT Vault Account
AutoRABIT Vault administrators can enable MFA either **globally for all users** or **individually per user**.
### Global MFA Enforcement
1. Log in to your **AutoRABIT Vault** account.
2. Navigate to **Manage Users > Users**.
3. Toggle the **MFA switch** in the header to enable MFA for all users in the account.
### Per-User MFA Enforcement
1. Navigate to **Manage Users > Users**.
2. Find the specific user in the list.
3. Enable MFA by sliding the **MFA toggle** to the right for that user.
{% hint style="info" %}
**Important Notes:**
* Enabling MFA does **not** affect users who are already logged in. MFA will be enforced at the next login.
* Users will be prompted to **register a mobile device** with an authenticator app (e.g., Google Authenticator, Salesforce Authenticator).
{% endhint %}
***
## Reset MFA
If a user loses their device or switches to a new phone, they must contact an administrator to reset their MFA setup.
### Admin Steps to Reset MFA:
1. Go to **Manage Users > Users**.
2. Locate the user and click the **Reset** icon next to the MFA toggle.
3. On the user's next login, they will be prompted to scan a **new QR code** to register their authenticator 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://knowledgebase.autorabit.com/product-guides/vault/getting-started/set-up-multifactor-authentication-in-vault.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.
