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

# Concepts

Explanations and definitions of the key Remote Desktop concepts

Explanations and definitions of the key Remote Desktop concepts: what it is, how to size it, connection modes, users, and data protection.

<table data-view="cards"><thead><tr><th></th><th></th><th data-hidden data-card-target data-type="content-ref"></th></tr></thead><tbody><tr><td><strong>What is Remote Desktop?</strong></td><td>What the remote work environment is, who it is for, and how you offer it to your client as a managed service.</td><td><a href="https://docs.plenit.com/docs-en/productos/remote-desktop/concepts/what-it-is.md">What Is Remote Desktop?</a></td></tr><tr><td><strong>Size your environment</strong></td><td>How to calculate concurrent users and host resources to size the environment.</td><td><a href="https://docs.plenit.com/docs-en/productos/servers/concepts/size-cpu-ram-disk.md">Size Your Server</a></td></tr><tr><td><strong>Connection modes</strong></td><td>The connection methods (RemoteApp, HTML5, and direct connection) and which one suits each user.</td><td><a href="https://docs.plenit.com/docs-en/productos/remote-desktop/details/connection-modes-compatibility.md">Connection Modes</a></td></tr><tr><td><strong>Users and applications</strong></td><td>How users, permissions, and the applications you publish in the environment are managed.</td><td><a href="https://docs.plenit.com/docs-en/productos/remote-desktop/concepts/users-and-applications.md">Users and Applications</a></td></tr><tr><td><strong>Access to the environment</strong></td><td>What the user sees when logging in and how their access is controlled, including 2FA.</td><td><a href="https://docs.plenit.com/docs-en/productos/remote-desktop/concepts/environment-access.md">Access to the Environment</a></td></tr><tr><td><strong>Backup and data protection</strong></td><td>How the environment is protected with backups, managed from the associated Servers subscription.</td><td><a href="https://docs.plenit.com/docs-en/productos/servers/concepts/backup-and-data-protection.md">Backup and Data Protection</a></td></tr><tr><td><strong>Glossary</strong></td><td>Definitions of Remote Desktop-specific terms.</td><td><a href="https://docs.plenit.com/docs-en/productos/remote-desktop/concepts/glossary.md">Glossary</a></td></tr></tbody></table>


---

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