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

# MFA

Learn more about how to enable MFA.

Multi-Factor Authentication (MFA) adds a second check to your North sign in. North supports two methods: an authenticator app, and a code sent by SMS.

## Enable MFA

1. Go to [app.north.cloud/settings](https://app.north.cloud/settings) and open the **Security** tab.
2. Find the **Multi-Factor Authentication** section.
3. Choose **Authenticator App** or **SMS**.
4. For an authenticator app, scan the QR code with your app, then enter the six-digit code it shows. If you cannot scan the code, use the setup key below it.
5. For SMS, enter your phone number, click **Send code**, then enter the code you receive.

{% hint style="info" %}
Your email address must be verified before you can enroll. If it is not, the Security tab offers to send you a verification email. Click the link in that email, then click refresh on the same panel.
{% endhint %}

## Require MFA for Your Team

The root user of your organization can make MFA mandatory. Enroll first, then set the **Require MFA for all team members** toggle in the same section. Team members who are not enrolled are asked to enroll at their next sign in.

## Remove MFA

In the **Multi-Factor Authentication** section, click the remove control and confirm. North signs you out when the removal completes, so you must sign in again.


---

# 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.north.cloud/docs/getting-started/security/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.