> For the complete documentation index, see [llms.txt](https://docs.noros.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.noros.ai/getting-started/security/multi-factor-authentication-mfa.md).

# Multi-Factor Authentication (MFA)

Multi-Factor Authentication adds an extra layer of security to your Noros account by requiring a second form of verification when signing in.

### Prerequisites

Your email address must be verified before you can enable MFA. If your email is not yet verified, you'll be prompted to verify it first.

### Enabling MFA

1. Go to **Settings > Profile**.
2. Scroll to the **Security** section.
3. Follow the prompts to enroll your phone number for SMS verification.

### How It Works

When MFA is enabled, you'll receive a verification code via **SMS** to your registered phone number each time you sign in. Enter the code to complete authentication.

### Organization Requirements

Your organization may require MFA for all members. If your organization enforces MFA, you'll be prompted to set it up before you can access the app.

### Managing MFA

You can enable or disable MFA at any time from **Settings > Profile**. If you lose access to your phone number, contact <support@noros.ai> for account recovery assistance.


---

# 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.noros.ai/getting-started/security/multi-factor-authentication-mfa.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.