> 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/how-to-associate-an-rd-user-with-a-domain-user.md).

# How to Associate a Remote Desktop User with an Existing Domain User

Link an environment user with an existing domain user to centralize management, from the user edit screen.

If you want to centralize the management of users in an environment in the client's corporate domain, you can associate each Remote Desktop user with an existing domain user.

That way, their identity and access are managed from the domain, not separately.

> #### 👍 What you get
>
> A Remote Desktop user linked to an existing domain user, with management centralized in the client's domain.

### Before you begin

* Access the administration panel at [admin.plenit.com](https://admin.plenit.com) with permissions on the environment.
* Have a Remote Desktop subscription with registered users. If you don't have one yet, set it up with the [the Remote Desktop Quick Start.](https://docs.plenit.com/docs-en/productos/remote-desktop/quickstart.md)
* Have previously joined the Remote Desktop server to the domain.

### Step 1. Enter the user edit screen

In [admin.plenit.com](https://admin.plenit.com), go to **Cloud Services → Remote Desktop** and enter the environment subscription. In the section **Users**, locate the user, open its menu **⋮** tab and click **Edit**.

![Edit a user from the Users section](https://3894148717-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FxksPMyYRDCe4qKkhbpcY%2Fuploads%2F6kmTsL0vPJLeo0jzhhCV%2Fescritorio-remoto-asociar-dominio-01.png?alt=media\&token=630b346a-1843-4e85-9fc9-12c025ca7ab7)

> #### 📘 Also from the organization
>
> You can reach the same subscription from the organization, in **Subscriptions**. The process is identical either way.

### Step 2. Open the user type selector

On the Edit user screen, look for the **Server user** section and click the **pencil** to choose how it will access the service.

![Server user section with the pencil](https://3894148717-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FxksPMyYRDCe4qKkhbpcY%2Fuploads%2Fkhdlymna6dOvYAOtTaFt%2Fescritorio-remoto-asociar-dominio-02.png?alt=media\&token=77a58bba-2aa1-4433-999d-a1d829bc0888)

The Server user window opens, where you choose the user type in Type of user. These are the options:

* **PLENIT user**: the platform's native user created when the service is provisioned. It is the default value.
* **Existing local user**: to reuse a user from an imported machine and make it compatible with the platform.
* **Domain user**: to link the user to an existing domain, which is the case in this guide.

### Step 3. Select Domain user and link it

Select **Domain user**. The window changes and asks you for the **username** of the existing user you are linking to. Enter it with the domain name in front, in the format DOMAIN\user. When you have it, click **Save**.

<figure><img src="https://3894148717-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FxksPMyYRDCe4qKkhbpcY%2Fuploads%2FUoCtCNx3TfneFKH4cz3C%2Fescritorio-remoto-asociar-dominio-03.png?alt=media&amp;token=4c219f27-c5e2-40aa-9b9c-63d2670692a4" alt="Ventana Server user con Usuario de dominio seleccionado y el nombre de usuario con el formato DOMINIO\usuario"><figcaption></figcaption></figure>

The platform confirms the change and you can continue with the rest of the users.

> #### ❗️ From this point on, passwords are managed in the domain
>
> Once the user is associated with a domain, the platform stops managing and syncing their password. Any change related to that user, starting with the password, is made from the domain server. Keep this in mind before making the change.

### Conclusion

Associating a user with a domain is a change of just a few clicks — edit the user, open the user type with the pencil, and choose Domain user — but with an important consequence: from that moment on, that user's identity and password live in the client's domain, not in the platform.

That's exactly what you're looking for when you want to centralize management, as long as you are clear that changes will now be made on the domain server. Repeat the process for each user you want to centralize.

### Next steps

* Register several users at once with [bulk user upload.](https://docs.plenit.com/docs-en/productos/remote-desktop/how-to/how-to-bulk-upload-users.md)
* Review connection modes and permissions in [Connection modes.](https://docs.plenit.com/docs-en/productos/remote-desktop/details/connection-modes-compatibility.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/how-to-associate-an-rd-user-with-a-domain-user.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.
