> 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 can access their applications from anywhere and on any device.

In this guide, you deploy the service, grant users access, and enter the environment.

> #### 📘 Before you start
>
> The deployment relies on the users in your organization. If you haven't created them yet, create them first and come back here.

### Requirements

* A logged-in Plenit account.
* An organization with users available to associate with the environment.

### Start setup

Depending on whether you already use Remote Desktop or it's 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 subscriptions list         |
| It's your first time with the service | On the product page, click **I want to try it now**                                                       |
| From a specific client                | Go into **Organization › Subscriptions** and choose **Remote Desktop** in "What do you want to register?" |

![Remote Desktop overview with the New subscription button](https://3894148717-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FxksPMyYRDCe4qKkhbpcY%2Fuploads%2Fgit-blob-ea655355ac7a7e6008439654956ea7870d7bd1e4%2F0_5.png?alt=media)

![Remote Desktop product page with the I want to try it now button](https://3894148717-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FxksPMyYRDCe4qKkhbpcY%2Fuploads%2Fgit-blob-f579b80b012accb2bd587416a899e1b99ed57bd1%2F0.png?alt=media)

### Step 1. Name the subscription

Assign a descriptive name to the subscription. It's the name you use to identify it in the dashboard and in billing. Continue when you have it.

<figure><img src="https://3894148717-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FxksPMyYRDCe4qKkhbpcY%2Fuploads%2Fgit-blob-ea66bfb43c8e90695c5e651238a547a991721297%2F1_5.png?alt=media" alt=""><figcaption></figcaption></figure>

### Step 2. Select the users with access

Select the users in your organization who will have access to the environment and continue.

<figure><img src="https://3894148717-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FxksPMyYRDCe4qKkhbpcY%2Fuploads%2Fgit-blob-f7be0f241071f7aeadaa069c452fa8a47070003c%2F1.png?alt=media" alt=""><figcaption></figcaption></figure>

### Step 3. Define the connection mode and permissions

For each user, define the **connection mode** and the **permission level**.

> #### 📘 Connection mode and permissions
>
> * **Application 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).<br>

<figure><img src="https://3894148717-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FxksPMyYRDCe4qKkhbpcY%2Fuploads%2Fgit-blob-26cf3bba1b5a3234821e1f1ee2e2a92906feed83%2F4_5.png?alt=media" alt=""><figcaption></figcaption></figure>

### Step 4. Set the concurrent users

Indicate the maximum number of users who can have a session open at the same time.

> #### 📘 Concurrent, not total
>
> The maximum number of concurrent users is the number of users with sessions open at the same time, not the total number of registered users. You can grant access to more users than connect at once and size it according to that peak.

<figure><img src="https://3894148717-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FxksPMyYRDCe4qKkhbpcY%2Fuploads%2Fgit-blob-2cd00b089743ce732fa130de5a1a9b051bc0499f%2F5.png?alt=media" alt=""><figcaption></figcaption></figure>

### 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.

<figure><img src="https://3894148717-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FxksPMyYRDCe4qKkhbpcY%2Fuploads%2Fgit-blob-c1da262b722b837701985a77627809cd5b56b6fc%2F6.png?alt=media" alt=""><figcaption><p>Select Your Applications</p></figcaption></figure>

<figure><img src="https://3894148717-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FxksPMyYRDCe4qKkhbpcY%2Fuploads%2Fgit-blob-188949328340b7796476dcb154716fa58a8896cf%2F7.png?alt=media" alt=""><figcaption><p>Assign Permissions to the User and Applications</p></figcaption></figure>

### Step 6. Review the sizing and save

We suggest a server sizing 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 workload grows, you can adjust the server configuration later.<br>

<figure><img src="https://3894148717-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FxksPMyYRDCe4qKkhbpcY%2Fuploads%2Fgit-blob-4a2a777e8967cb57487eb9b1471fdb319c92345f%2F8.png?alt=media" alt=""><figcaption></figcaption></figure>

### Step 7. Configure your Access Portal.

Set up your branding and custom URL to access the Remote Desktop portal,

you can customize everything from your branding to the default corporate configuration.

<figure><img src="https://3894148717-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FxksPMyYRDCe4qKkhbpcY%2Fuploads%2Fgit-blob-95cdc82071719d0e84c48bcf0b904568593094d9%2F12.png?alt=media" alt=""><figcaption></figcaption></figure>

### 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
>
> Although the cards appear in the dashboard, the service is not available until the process finishes. Wait until it completes before accessing it.<br>

<figure><img src="https://3894148717-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FxksPMyYRDCe4qKkhbpcY%2Fuploads%2Fgit-blob-04560c17cd3fcab65e3d146613fdc0173b23e5d0%2FFinal.png?alt=media" alt=""><figcaption></figcaption></figure>

### Step 8. Access the environment

When the deployment finishes, the registered users receive their access details by email. From the subscription, you have access to the service to enter the environment.

<figure><img src="https://3894148717-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FxksPMyYRDCe4qKkhbpcY%2Fuploads%2Fgit-blob-792d1814a28965d6ebac07800c15eddb0698bdf4%2F13.png?alt=media" alt=""><figcaption></figcaption></figure>

> #### 👍 Environment ready
>
> Your Remote Desktop environment is up and running, and your users log in with their credentials from any device with an internet connection.

### Check

* 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](https://docs.plenit.com/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](https://docs.plenit.com/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 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/quickstart.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.
