> 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

If you want to centralize user management for an environment in the customer’s corporate domain, you can associate each Remote Desktop user with an existing domain user.

This 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 customer’s domain.

### Before you start

* Access the admin 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 [Remote Desktop Quick Start.](/docs-en/productos/remote-desktop/quickstart.md)
* Have previously joined the Remote Desktop server to the domain.

### Step 1. Go to 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**, find the user, open its menu **(...)** menu **and click**.

{/\* 📸 SCREENSHOT 1 · Users section · user menu (…) › Edit \*/}

![Edit a user from the Users section](https://REEMPLAZA-URL/escritorio-remoto-asociar-dominio-01.png)

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

### Step 2. Open the user type selector

In the user profile, look for the section **Server User** and click the **magnifying glass** to choose how the service will be accessed.

{/\* 📸 SCREENSHOT 2 · user profile · highlight "Server User" and the magnifying glass \*/}

![Server User section with the magnifying glass](https://REEMPLAZA-URL/escritorio-remoto-asociar-dominio-02.png)

A window opens to select the user type. These are the options:

* **Plenit User**: the platform’s native user created when the service is provisioned. This 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 for the **login name** of the existing user you are linking to. If the link is to a domain user, include the domain name in that value. When you have it, click **Save**.

{/\* 📸 SCREENSHOT 3 · Domain User selection · login field with the domain \*/}

![Domain User selection and login entry](https://REEMPLAZA-URL/escritorio-remoto-asociar-dominio-03.png)

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

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

### Conclusion

Associating a user with a domain is a matter of a few clicks — edit the user, open the user type with the magnifying glass, and choose Domain User — but with an important consequence: from that moment on, the identity and password of that user live in the customer’s domain, not in the platform.

This is exactly what you want when you need 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

* Create several users at once with the [bulk user upload.](/docs-en/productos/remote-desktop/how-to/how-to-bulk-upload-users.md)
* Review the connection modes and permissions in [Connection modes.](/docs-en/productos/remote-desktop/details/connection-modes-compatibility.md)
* Manage the rest of the environment from [How to manage your Remote Desktop environment.](/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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
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=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.