> 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.md).

# Multi-Factor Authentication

Multi-Factor Authentication (MFA) adds a second check to your sign-in. In addition to entering your password when you log  into your account, you also need to enter either:

* A code from an authenticator app on your phone.
* An email code (this is back-up option when you do not have access to your phone).

{% hint style="info" %}
You may also see MFA referred to as 2FA (Two-Factor Authentication). On the Clickatell platform they mean the same thing.
{% endhint %}

### Before you enable MFA for your account:

1. Tell your users first. Once MFA is on, every user must enrol at their next sign-in.
2. Confirm your users can install an authenticator app, particularly where devices are managed by IT. 
3. Check that every user's registered email address in Clickatell is correct and reachable — this is the backup if someone loses their phone. 
4. Make sure your account has more than one administrator. 

{% hint style="info" %}
Avoid enabling MFA at the start of a busy shift. Contact-centre teams in particular will all enrol at once, and enrolment takes a few minutes per person.
{% endhint %}

#### Supported authenticator apps

* Google Authenticator
* Microsoft Authenticator
* Authy
* 1Password


---

# 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.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.