> 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/quickstart.md).
# Quick Start
With Remote Desktop you set up a work environment where your users access their applications from anywhere and on any device.
In this guide you deploy the service, give users access, and enter the environment.
> #### 📘 Before you start
>
> The deployment relies on the users in your organization. If you have not created them yet, create them first and come back here.
### Requirements
* A Plenit account with an active session.
* An organization with users available to associate with the environment.
### Start the setup
Depending on whether you already work with Remote Desktop or it is your first time, you reach the wizard through one of these paths. All three end up in the same place.
| Situation | How you start |
| -------------------------------------- | -------------------------------------------------------------------------------------------------------- |
| You already use Remote Desktop | Go into Remote Desktop and click **New subscription**, at the top right of the subscription list |
| It is your first time with the service | On the product page, click **I want to try it now** |
| From a specific client | Go to **Organization › Subscriptions** and choose **Remote Desktop** under "What do you want to set up?" |
### Step 1. Name the subscription
Assign a descriptive name to the subscription. This is the name you use to identify it in the dashboard and in billing. Continue when you have it.
### Step 2. Select the users with access
Mark the users in your organization who will have access to the environment and continue.
### Step 3. Define the connection mode and permissions
For each user, define the **connection mode** and the **permission level**.
> #### 📘 Connection mode and permissions
>
> * **Applications Launchpad**: the user sees and opens only the applications you publish to them, without a desktop. Lighter and more focused on their work.
> * **Remote Desktop**: the user accesses a full Windows desktop, as if it were their work computer.
> * **Permissions**: User (works with their applications) or Administrator (also manages the environment).
### Step 4. Set the concurrent users
Indicate the maximum number of users who can have the session open at the same time.
> #### 📘 Concurrent, not total
>
> The maximum number of concurrent users is the number of users with an open session at the same time, not the total number of users set up. You can give access to more users than those who connect at the same time and size it according to that peak.
### Step 5. Add Marketplace applications and permissions
Choose the Marketplace applications you want to preinstall and associate each user with the ones they will use. Applications that are not in the Marketplace are installed later from the console.
Select Your Applications
Assign Permissions to the User and Applications
### Step 6. Review the sizing and save
We suggest a server size based on the number of users and applications. Accept it or choose another configuration, and save to launch the deployment.
> #### 📘 How it is calculated
>
> The recommendation is based on the number of users and the planned applications. If your load grows, you can adjust the server configuration later.
### Step 7. Configure your Access Portal.
Configure your brand and your custom URL to access the Remote Desktop portal,
you can configure everything from your branding to the default corporate configuration.
### Step 8. Wait for the deployment
The deployment takes a few minutes: the machines are created, the users are configured, and the applications are installed.
> #### 🚧 Deployment in progress
>
> Even if the cards appear in the dashboard, the service is not available until the process finishes. Wait for it to complete before accessing it.
### Step 8. Access the environment
When the deployment ends, the set-up users receive their access details by email. From the subscription, you have access to the service to enter the environment.
> #### 👍 Environment ready
>
> Your Remote Desktop environment is up and running, and your users sign in with their credentials from any device with an internet connection.
### Verify
* The service appears active in the subscription.
* Users receive the email with their access details.
* A user enters the environment from the access link.
### Next steps
* Manage the environment and users: [Administrator guide](/docs-en/productos/remote-desktop/how-to/how-to-administer-your-remote-desktop.md)
* Install an application that is not in the Marketplace: [Console installation ](/docs-en/productos/remote-desktop/how-to/how-to-install-and-publish-an-application.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/quickstart.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.