> For the complete documentation index, see [llms.txt](https://help.clickatell.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.clickatell.com/clickatell-user-portal/user-portal/multi-factor-authentication/how-to-enable-mfa-on-your-account.md).

# How to enable MFA on your account

Only an Account Administrator can set up MFA. It is set up for the whole account, and individual users cannot opt out or skip it. This is deliberate: a security control that some people can decline does not reliably protect the account.

1. In the Clickatell portal, go to your account security settings and find the Multi-Factor Authentication section.  
2. Select the option to enable MFA. 
3. Read the confirmation dialog. It explains that MFA will apply to all users on the account and that no one can opt out. 
4. Confirm. MFA is now active — no code is required from you at this step. 

From this point, each user is guided through enrolment the next time they sign in. Users already signed in are not interrupted mid-session. <br>

The MFA settings page shows how many users have finished enrolling, for example “3 of 8 users enrolled”. A user counts as enrolled only once both their authenticator app and their email backup are confirmed. Deactivated users are not counted.


---

# 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://help.clickatell.com/clickatell-user-portal/user-portal/multi-factor-authentication/how-to-enable-mfa-on-your-account.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.