> For the complete documentation index, see [llms.txt](https://docs.devolutions.net/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.devolutions.net/rdm/knowledge-base/how-to-articles/configure-google-authenticator-2-factor-authentication.md).

# Configure Google Authenticator 2-factor authentication

Configure Google Authenticator two-factor authentication in Remote Desktop Manager to add a security layer at application startup.

{% embed url="<https://youtu.be/Oi27Y8FfcNg>" %}

Remote Desktop Manager has the option to use Google Authenticator to provide an additional security layer when the application starts.

{% hint style="success" %}
Before you start the configuration, make sure you have installed the [Google Authenticator application](https://support.google.com/accounts/answer/1066447?hl=en) on your mobile device.
{% endhint %}

1. Click on ***File – Settings – Security*** and select ***Require a TOTP validation (Devolutions Password Manager or Google Authenticator)*** in the ***2-factor authentication*** section. Then, click on ***Configure*** to set up your Google Authentication.
2. Scan the QR code on your screen with the Google Authenticator application to setup Remote Desktop Manager in Google Authenticator. When Remote Desktop Manager is configured in Google Authenticator, enter the validation code provided by Google Authenticator in Remote Desktop Manager.
3. When the validation code is entered, click on ***Validate***, then ***Ok***.
4. Relaunch Remote Desktop Manager to be prompted for the Google Authenticator code.

{% hint style="info" %}
Google Authenticator generates a new validation code every 30 seconds. There will be a color indicating the end of the time window is approaching, please consult the application documentation of your device for complete information.
{% 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://docs.devolutions.net/rdm/knowledge-base/how-to-articles/configure-google-authenticator-2-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.