> For the complete documentation index, see [llms.txt](https://docs.plenit.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.plenit.com/docs-en/productos/remote-desktop/how-to/como-configurar-2fa-a-los-usuarios-de-escritorio-remoto.md).

# How to Configure 2FA for Remote Desktop Users

Enable two-factor authentication for a user from the dashboard and guide them through registering their authenticator app so they can sign in with a temporary code.

Two-factor authentication (2FA) adds a layer of security to access: in addition to your username and password, the person needs a temporary code generated by an app on their phone that changes every so often. That way, even if someone saw the code, it would stop working within minutes.

This guide has two parts: the activation you do as administrator, and the registration completed by the user.

> #### 👍 What you get
>
> 2FA activated for a Remote Desktop user, and the user registered in their authenticator app to access with a temporary code.

### Before you begin

* Access the administration panel at [admin.plenit.com](https://admin.plenit.com) with permissions on the environment.
* Have an active Remote Desktop subscription. If you don't have one yet, set it up with the [Remote Desktop Quick Start.](https://docs.plenit.com/docs-en/productos/remote-desktop/quickstart.md)
* The user must have a smartphone with an authenticator app installed: Google Authenticator or Microsoft Authenticator.

> #### 📘 One 2FA for all your environments
>
> If a user has access to more than one Remote Desktop, a single 2FA is enough to access all of them. They do not need to register one per environment.

### Step 1. Activate the user's 2FA (administrator)

In [admin.plenit.com](https://admin.plenit.com), go to **Cloud Services → Remote Desktop** and enter the environment subscription. Open the tab **Users**, select the server you are going to work on, find the user and check their **2FA checkbox**.

![Activation of the 2FA checkbox on the user](https://3894148717-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FxksPMyYRDCe4qKkhbpcY%2Fuploads%2Fgit-blob-c6f986e478ee2b10e040a213c87a73fde0142af0%2FCAPTURA%201%20%C2%B7%20Users%20%C2%B7%20servidor%2C%20usuario%20y%20check%20de%202FA.jpg?alt=media)

A notice about 2FA activation appears. Click **Confirm** to continue. The check turns green, indicating that 2FA is active for that user.

![Confirmation of 2FA activation](https://3894148717-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FxksPMyYRDCe4qKkhbpcY%2Fuploads%2Fgit-blob-bd38fa0d7bbdd3c7f207cf6f7b22309f11771a90%2FCAPTURA%202%20%C2%B7%20aviso%20de%20activaci%C3%B3n%20%C2%B7%20bot%C3%B3n%20Confirm.jpg?alt=media)

That completes your part. The user completes the rest at their next login.

### Step 2. Registration in the authenticator app (user)

The next time the user enters their Remote Desktop, with the authenticator app open on their phone, they will see a screen with two ways to register. They only need one:

* **Alphanumeric key**: enter it manually in the app to register access.
* **QR code**: scan it with the app to register access.

After registering by either method, click **Confirm**. From then on, the app will show the temporary access code.

![User registration with alphanumeric key or QR](https://3894148717-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FxksPMyYRDCe4qKkhbpcY%2Fuploads%2Fgit-blob-25ac94f18621093c48bee4a5782f7db3ca3f024c%2FCAPTURA%203%20%C2%B7%20pantalla%20con%20clave%20alfanum%C3%A9rica%20y%20QR%20para%20registrar%20la%20app.jpg?alt=media)

> 📘 If the user is on server and load balancer
>
> When the user is registered on a server and, in addition, on the load balancer, they will see an option to choose where to connect. If they are only on a server or only on the load balancer, they do not have to choose.

Then, the user chooses the connection method: **HTML5** if they enter through the browser, or **RemoteApp** if they prefer the client (this requires downloading a plugin and, therefore, administrator permissions on their computer). Click **Connect** to launch the connection.

Finally, in the validation window, enter the **authentication code** shown by the app, and log in.

![Entering the authentication code](https://3894148717-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FxksPMyYRDCe4qKkhbpcY%2Fuploads%2Fgit-blob-4757e515e46516f114ffb1e5cc6f730f5a0dbcc4%2FCAPTURA%204%20%C2%B7%20ventana%20de%20validaci%C3%B3n%20%C2%B7%20introducir%20el%20c%C3%B3digo%20de%20la%20app.jpg?alt=media)

> #### 📘 Reconfigure 2FA later
>
> Once 2FA is activated, the user's profile in the Organization section adds two options: reconfigure the authenticator app by generating a new key, or generate one-time-use codes. These are useful if the user changes phones or loses access to the app.

### Conclusion

Activating 2FA is a quick change on your part — check the user's box in Users and confirm — but its effect is completed by the user when they register the app on their phone with the key or QR code. From then on, each login requests the temporary code, and a single 2FA covers all the environments that user has access to.

If they ever lose access to the app, they can regenerate the key or request one-time-use codes from their profile in Organization.

### Next steps

* Strengthen access by avoiding open ports in [How to configure the ports of your Remote Desktop.](https://docs.plenit.com/docs-en/productos/remote-desktop/how-to/how-to-configure-remote-desktop-ports.md)
* Create or manage users in bulk with the [bulk user upload.](https://docs.plenit.com/docs-en/productos/remote-desktop/how-to/how-to-bulk-upload-users.md)
* Manage the rest of the environment from [How to manage your Remote Desktop environment.](https://docs.plenit.com/docs-en/productos/remote-desktop/how-to/how-to-administer-your-remote-desktop.md)


---

# 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.plenit.com/docs-en/productos/remote-desktop/how-to/como-configurar-2fa-a-los-usuarios-de-escritorio-remoto.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.
