> 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-reset-a-users-mfa.md).

# How to reset a user's MFA

When someone has lost, replaced, or wiped the device with their authenticator app on it, an Account Administrator can reset their MFA as follows:

1. Open the user's profile on the Clickatell portal. 
2. Select Reset MFA. 
3. Confirm using your own current MFA code. This step exists so that a hijacked administrator session cannot quietly reset other people. 
4. The user's authenticator and email backup are cleared, and all of their trusted devices are revoked. 

The user enrols again from scratch at their next sign-in, and is notified by email that their MFA was reset.

{% hint style="info" %}
 Resetting a user's MFA does not exempt them from using MFA. MFA remains active for the account. 
{% 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-reset-a-users-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.