> 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-bulk-upload-users.md).
# How to Bulk Upload Users in Remote Desktop
When you need to create several accounts at once, bulk upload saves you from creating them one by one: you prepare a CSV file with the users, import it, and then complete their assignment and configuration in the environment.
> #### 👍 What you get
>
> Several users created in the Remote Desktop environment from a single CSV, ready to be assigned with the management wizard.
### Before you start
* Access the admin 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.](/docs-en/productos/remote-desktop/quickstart.md)
In [admin.plenit.com](https://admin.plenit.com), go to **Cloud Services → Remote Desktop** and enter the environment subscription. In the section **Users**, top right, click **Import Users**.
{/\* 📸 CAPTURE 1 · Users section · highlight the Import Users button \*/}
> #### 📘 Also from the organization
>
> You can reach the same subscription from the organization, in **Subscriptions**. Use whichever route is more convenient for you; the rest of the process is identical.
To create a single user or modify an existing one, you don't need bulk upload: do it from manual user management.
### Step 2. Download and fill in the CSV template
In the **Import Users**, click **Download this file** to download the template `bulk_import_users.csv`. The window doesn't close after downloading, so you can leave it open while you prepare the file (it only closes if you click outside it).
{/\* 📸 CAPTURE 2 · Import Users window · highlight Download this file \*/}
#### 2.1 The file fields
Treat the file as a **comma-separated CSV**. Each line is a new user, with these fields:
* **Name**: user's first name.
* **LastName**: user's last name.
* **Email**: user's email address.
* **2FA**: whether two-factor authentication will be enabled. Optional.
* **Position**: job title. Optional.
* **Phone**: phone number. Optional.
#### 2.2 How each line is written
For a user `David Hasselhoff`, with email `dhasselhoff@plenit.com`, 2FA enabled, position `Marketing` and phone `888888888`, the line is:
```
David,Hasselhoff,dhasselhoff@plenit.com,True,Marketing,888888888
```
> #### 🚧 Keep the commas for empty fields
>
> If you leave an optional field empty, keep its comma so the CSV maintains the structure. For example, with only the required data and the phone number, the line looks like this: `David,Hasselhoff,dhasselhoff@plenit.com,,,888888888`.
### Step 3. Upload the file and import it
Back in the **Import Users**, click **Upload Files**, select your CSV and open it. If the format is correct, you'll see a green indicator next to the file name; if there is a problem, it will appear in red. With the green indicator, click **Import users**.
{/\* 📸 CAPTURE 3 · CSV validation in green · highlight Import users \*/}
When finished, the platform offers two paths:
* **Add to subscription**: add the users to the subscription at that very moment.
* **Not now**: postpone the assignment to do it later.
If you choose **Add to subscription**, you jump straight to server and user configuration (Step 5). If you choose **Not now**, you continue with Step 4 to assign them whenever you want.
{/\* 📸 CAPTURE 4 · Add to subscription / Not now choice \*/}
### Step 4. Open the assignment wizard
If you chose **Not now**, you return to **Users**. Click **Manage users** to open the wizard **User Management**.
Select the **server** where you will assign the users and click **Next**. Then select the **users** to whom you will apply the same configuration and click **Next**Next **New User**.
{/\* 📸 CAPTURE 5 · User Management · selection of server and users \*/}
> #### 📘 Same configuration per server
>
> The wizard applies the same configuration to the group of users you select. If you need to configure them on multiple servers, repeat the process on each one.
>
> To link users to an existing domain, follow [How to associate a Remote Desktop user with a domain user.](/docs-en/productos/remote-desktop/how-to/how-to-associate-an-rd-user-with-a-domain-user.md)
### Step 5. Define access, user type, and security
Configure how the selected users will access the environment:
* **Remote App**: the user only sees the application launchers.
* **Virtual Desktop**: the user accesses a full desktop.
Then choose the user type, **User** (standard) or **Administrator** (with administrator permissions). In **Type of user** you define whether it belongs to a domain or whether it is a leftover user; if you do not select the domain option, the user is created locally and is deleted if the server it is linked to is deleted. In **Security** you can enable **two-factor authentication**. When you're done, click **Next**.
{/\* 📸 CAPTURE 6 · access, user type, and security options \*/}
### Step 6. Assign applications and confirm
Select the applications that the chosen users will have by clicking each one, and click **Save**. On the **Summary**, review all the changes and, when they are correct, click **Confirm Changes**.
{/\* 📸 CAPTURE 7 · application assignment and Summary with Confirm Changes \*/}
If everything went well, the new users appear created in the Remote Desktop subscription.
### Conclusion
Bulk upload solves the creation of many accounts in two stages: first you import the CSV with each user's data, and then you assign and configure them with the wizard.
The part that the process cares about most is the file: keep the commas for empty fields and check that validation turns green before importing.
From there, the wizard lets you apply access, permissions, security, and applications to the group all at once. For one-off creations or to link users to a domain, continue with manual user management.
---
# 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-bulk-upload-users.md?ask=&goal=
```
`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.