> 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-set-up-mfa-for-each-user.md).

# How to set up MFA for each user

This step takes places after MFA has been[ enabled for the account](/clickatell-user-portal/user-portal/multi-factor-authentication/how-to-enable-mfa-on-your-account.md). Prior to individual set up, each user must already have installed a [supported](/clickatell-user-portal/user-portal/multi-factor-authentication/how-to-enable-mfa-on-your-account.md) authenticator app on their device.  In addition to this, they must have access to the email address that they use to sign in to Clickatell.

{% hint style="info" %}
First time set up will take approximately 5 minutes.
{% endhint %}

**These are the steps that each user must follow:**

**Connect an authenticator app**

1. Sign in to your Clickatell account.
2. A QR code will be displayed. Open your authenticator app and choose the option to add an account, then scan the QR code.
   * If you cannot scan it, select the option to enter a key manually and type the key shown on screen into your app instead.
3. Your app now shows a 6-digit code for Clickatell that changes every 30 seconds. Type the current code into the platform and continue.

**Confirm a backup email address**

1. A 6-digit code is emailed to your registered address. 
2. Enter that code to confirm the backup works. 
3. If it does not arrive within a minute, check your spam or junk folder, then use Resend code. 

Setup is complete once both steps are confirmed. You are signed in as normal. The next time that you sign in, you will be prompted to enter a code. 

{% hint style="info" %}
If you close the browser after connecting your app but before confirming your email, your app stays connected. Next time you sign in you continue from the email step — you do not need to scan the QR code again. 
{% endhint %}

**Remember this device**

On the verification screen there is a Remember this device checkbox. It is unticked by default.

If you leave it unticked, you will be required to enter a new code every time that you sign in. If you tick it, you will not be prompted to enter a code for 30 days (trust period), on that particular browser and device. You will still need to enter a password, as usual.

Trust ends early if you clear your browser cookies, use a different browser or device, or your administrator resets your MFA. At the end of the trust period you are asked for a code again, and you can choose to trust the device once more.

{% hint style="warning" %}
Do not tick this on a shared, public, or hot-desk computer. Anyone who later uses that machine and has your password would be able to sign in without a MFA code. If you are on a shared workstation, leave it unticked.
{% endhint %}


---

# 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-set-up-mfa-for-each-user.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.