> 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/da/knowledge-base/how-to-articles/configure-google-authenticator-2-factor-authentication.md).

# Konfigurer tofaktorgodkendelse med Google Authenticator

Konfigurer tofaktorgodkendelse med Google Authenticator i Remote Desktop Manager for at tilføje et sikkerhedslag ved programmets start.

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

Remote Desktop Manager kan bruge Google Authenticator til at tilføje et ekstra sikkerhedslag, når programmet starter.

{% hint style="success" %}
Før De starter konfigurationen, skal De sørge for at have installeret [Google Authenticator-programmet](https://support.google.com/accounts/answer/1066447?hl=en) på Deres mobilenhed.
{% endhint %}

1. Klik på ***Fil – Indstillinger – Sikkerhed***, og vælg ***Kræv en TOTP-validering (Devolutions Password Manager eller Google Authenticator)*** i afsnittet ***Tofaktorgodkendelse***. Klik derefter på ***Konfigurer*** for at konfigurere Deres Google-godkendelse.
2. Scan QR-koden på skærmen med Google Authenticator-programmet for at konfigurere Remote Desktop Manager i Google Authenticator. Når Remote Desktop Manager er konfigureret i Google Authenticator, skal De angive den valideringskode, som Google Authenticator viser, i Remote Desktop Manager.
3. Når valideringskoden er angivet, skal De klikke på ***Valider*** og derefter på ***OK***.
4. Start Remote Desktop Manager igen for at blive bedt om koden fra Google Authenticator.

{% hint style="info" %}
Google Authenticator genererer en ny valideringskode hvert 30. sekund. En farve angiver, at tidsvinduet nærmer sig slutningen. Se dokumentationen til programmet på Deres enhed for at få de fulde oplysninger.
{% 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/da/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.