> 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-administer-your-remote-desktop.md).

# How to Manage Your Remote Desktop Environment

The Remote Desktop subscription is the service administration center.

From there you review the status of the environment, manage users, install and assign applications, and control concurrent access. This guide walks through each section.

> #### 👍 What do you get
>
> Manage your Remote Desktop environment end to end — users, applications, licenses, and access — from a single place.

### Before you begin

* Access the administration panel at [admin.plenit.com](https://admin.plenit.com) with permissions on the environment.
* Have a Remote Desktop environment already set up. If you don't have one yet, set it up with the [Quick Start for Remote Desktop](https://gitlab.com/plenit-group/plenit-docs-es-es/-/blob/v1.0/docs/Productos/servicios-cloud-escritorio-remoto/servicios-cloud-escritorio-remoto-how-to/servicios-cloud-escritorio-remoto-inicio-rapido/README.md) .

> #### 📘 One environment, two subscriptions
>
> When the environment is set up, two subscriptions are created that work together: the **Remote Desktop** (users, permissions, connection modes, applications, and licenses) and the **Servers** (the host underneath: scaling, reboots, firewall, and backups). 
>
> This guide covers the first one. You have it explained in [The environment.](/docs-en/productos/remote-desktop/details/environment.md)

### Step 1. Sign in to the Remote Desktop subscription

In [admin.plenit.com](https://admin.plenit.com), go to **Cloud Services**, open **Remote Desktop** and enter the subscription for the environment you are going to manage, in **Subscriptions**.

You access the **Summary**, with the overall status of the service and access to the rest of the admin subsections.

{/\* 📸 SCREENSHOT 1 · Remote Desktop subscription summary \*/}

![Remote Desktop subscription summary](https://REEMPLAZA-URL/escritorio-remoto-administrar-01.png)

### Step 2. Manage users

In the **Users** you control, for each person in the environment:

* The **session status** (if they have a session open).
* The **connection mode** to the environment.
* The **permissions** assigned (User or Administrator).
* The **applications** that are visible to them.

{/\* 📸 SCREENSHOT 2 · Users section · highlight the status, mode, permissions, and apps columns \*/}

![Environment user management](https://REEMPLAZA-URL/escritorio-remoto-administrar-02.png)

How connection modes and permissions differ is covered in [Connection modes.](/docs-en/productos/remote-desktop/details/connection-modes-compatibility.md)

### Step 3. Install and assign applications

In the **Applications** you install, manage, and assign the environment software, and choose which users see each application.

{/\* 📸 SCREENSHOT 3 · Applications section · management and assignment \*/}

![Environment application management](https://REEMPLAZA-URL/escritorio-remoto-administrar-03.png)

> #### 📘 If you need an application that is not available
>
> You can install any application in the environment via the console. 
>
> You have it step by step in [How to install an application via the console.](/docs-en/productos/remote-desktop/how-to/how-to-install-and-publish-an-application.md)

### Step 4. Adjust concurrent access licenses

In the **Licenses** you define how many users can have a session open at the same time. Remember that Remote Desktop is billed per concurrent user, not per total number of users set up, so this is the number you size according to the client's usage peak.

{/\* 📸 SCREENSHOT 4 · Licenses section · adjust the maximum number of concurrent users \*/}

![Concurrent user license adjustment](https://REEMPLAZA-URL/escritorio-remoto-administrar-04.png)

How to estimate the peak and size without overshooting is in [Licensing and billing.](/docs-en/productos/remote-desktop/details/licensing-and-billing.md)

### Step 5. Give users access

For a user to enter their environment, share the user portal URL with them and verify that their credentials and permissions are already configured.

{/\* 📸 SCREENSHOT 5 · user access data to share \*/}

![Each user's access to their environment](https://REEMPLAZA-URL/escritorio-remoto-administrar-05.png)

The path the user follows when signing in is in [How to access your Remote Desktop (user guide)](/docs-en/productos/remote-desktop/how-to/user-quickstart-guide.md), which you can pass along as is.

### Conclusion

All service administration — users, permissions, applications, and licenses — is centralized in the Remote Desktop subscription, within Cloud Services.

The host underneath is managed from its Servers subscription, with the tasks specific to that product. Once the two subscriptions and what each one is for are clear, day-to-day environment management is handled from a single place.


---

# 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-administer-your-remote-desktop.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.