> 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/concepts/users-and-applications.md).

# Users and Applications

Who you grant access to the environment and what applications you publish, and how each user is associated with the applications they use

A Remote Desktop environment is based on two intersecting pieces: the **users** users you grant access to and the **applications** that you publish. Each user sees and uses only the applications you associate with them.

### Users

You grant access to the users in your organization: they are the same people you already manage there, whom you now enable to enter the environment. For each one, you define their connection method and permissions, as you can see in [Connection modes and permissions.](https://docs.plenit.com/docs-en/productos/remote-desktop/concepts/connection-modes.md)

* You register them **one by one** or in **bulk upload** when there are many of them.
* If the environment is integrated with a **domain**, you can **associate the Remote Desktop user with their domain account (Active Directory)**.

### Applications

The applications you publish live in the section **Applications** of the environment. For each one, you control:

* **Name**: how it is shown to the user within the environment.
* **Category**: the type of application (database, utilities, etc.).
* **Source**: whether it comes from the **Marketplace** or from a **manual installation**.
* **Users**: who has access to it.

You have two ways to bring software into the environment:

* **Marketplace**: preconfigured applications that you add in a few steps.
* **Manual installation**: any other application, installed via console on the environment's server.

> #### 📘 Publishing is installing and granting access
>
> Publishing an application has two parts: installing it in the environment and associating it with the users who will use it. Until you associate it with a user, that user will not see it.

### How users and applications intersect

Each user only sees the applications you associate with them. This way, the same environment serves different profiles: the administration team sees their ERP, the sales team sees their CRM, and no one sees what isn't theirs.


---

# 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/concepts/users-and-applications.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.
