> For the complete documentation index, see [llms.txt](https://help.cerby.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.cerby.com/tips-and-troubleshooting/video-gallery/accounts/video-how-to-turn-on-mfa-for-an-account-manually.md).

# \[Video] How to turn on MFA for an account manually

This article describes how to turn on MFA with Cerby as an authenticator app for your account.

***

## Key concepts

* Multi-factor authentication (MFA) is a second layer of protection for your accounts. When you configure Cerby as an authenticator app for MFA, Cerby generates time-based one-time passwords (TOTPs) for your account and distributes them during login to all users with shared access to the account. For more information, read the article [Explore the Cerby-managed verification methods for your accounts](/tips-and-troubleshooting/best-practices/accounts/explore-the-cerby-managed-verification-methods-for-your-accounts.md).
* Only account **Owners** can turn on MFA for an account through Cerby.
* For the setup, you need access to your app, to the Cerby web app, and Cerby mobile app. You can scan a QR code or provide a secret key.

{% embed url="<https://play.vidyard.com/GBivnLjpdnqui1WPPu5UHD>" %}


---

# 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.cerby.com/tips-and-troubleshooting/video-gallery/accounts/video-how-to-turn-on-mfa-for-an-account-manually.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.