> 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/glossary.md).

# Glossary

Remote Desktop terms, grouped by section and explained in tables.

A quick review of the terms we use when talking about Remote Desktop. If you come across one and aren't clear on it, look it up here.

### Environment and servers

| Term            | What it is                                                                                     |
| --------------- | ---------------------------------------------------------------------------------------------- |
| Environment     | The set of servers, users, and applications that make up a Remote Desktop for an organization. |
| Server (host)   | The Windows server that serves the users' sessions in the environment.                         |
| Multi-server    | Environment with more than one server, to distribute the load across several.                  |
| Load balancer   | Distributes users' sessions among the servers in a multi-server environment.                   |
| Server template | Reusable base configuration for deploying consistent environments.                             |

### Users and access

| Term              | What it is                                                                               |
| ----------------- | ---------------------------------------------------------------------------------------- |
| Concurrent user   | User with a session open at the same time; this is what determines the load and billing. |
| Session           | The active connection between a user and the environment.                                |
| Connection mode   | How the user enters and what they see (application Launchpad or full desktop).           |
| RemoteApp         | The applications in the environment run integrated with the user's Windows computer.     |
| HTML5             | Access to the environment from the browser, for any operating system.                    |
| Direct connection | Access from the user's desktop (RDP or RemoteApp), without going through the portal.     |
| User portal       | The web page from which the user enters their applications or their desktop.             |
| 2FA               | Two-step verification to strengthen each user's access.                                  |

### Applications

| Term                | What it is                                                                            |
| ------------------- | ------------------------------------------------------------------------------------- |
| Publish             | Install an application in the environment and associate it with the users who use it. |
| Marketplace         | Catalog of preconfigured applications ready to add.                                   |
| Manual installation | Installation of any application via console on the server.                            |

### Administration

| Term         | What it is                                                                                          |
| ------------ | --------------------------------------------------------------------------------------------------- |
| Subscription | The relationship that groups and bills the Remote Desktop service.                                  |
| Permissions  | The level for each user, User or Administrator (the latter with Windows administrator permissions). |

### Next steps

* Go back to [Concepts.](https://docs.plenit.com/docs-en/productos/remote-desktop/concepts.md)
* See the reference at [Details.](https://docs.plenit.com/docs-en/productos/remote-desktop/details.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/concepts/glossary.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.
