> 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/details/connection-modes-compatibility.md).

# Connection Modes

Modes, connection paths, compatible devices, and permissions, in reference tables.

For each user you decide three things: the **mode** (what they see), the **connection method** (how their session travels) and the **permissions**.

These three decisions define their experience and from which device they can work. For the conceptual framework, go to [Connection modes and permissions.](https://docs.plenit.com/docs-en/productos/remote-desktop/concepts/connection-modes.md)

### Mode: what the user sees

The mode decides whether the user works with a full desktop or only with their applications.

| Mode                  | What they see                           | Fits when                                                                       |
| --------------------- | --------------------------------------- | ------------------------------------------------------------------------------- |
| Application Launchpad | Only published applications, no desktop | The user needs a few specific applications and focused access                   |
| Remote Desktop        | A full Windows desktop                  | The user works as if on an office PC, with several tools and the desktop itself |

### Connection methods

The method decides how the session reaches the user and from which device they can connect. The key difference is the degree of integration with their device and whether or not anything needs to be installed.

| Method            | Access                              | Devices                      | Integration with the device                                                    | What it solves                                         |
| ----------------- | ----------------------------------- | ---------------------------- | ------------------------------------------------------------------------------ | ------------------------------------------------------ |
| RemoteApp         | User portal                         | Windows                      | High: apps behave almost like local ones (taskbar, Alt-Tab, multiple monitors) | The best experience on Windows devices                 |
| HTML5             | User portal                         | Windows, Mac, Linux, Android | Medium: everything runs inside the browser                                     | Access without installing anything and from any system |
| Direct connection | No portal (RDP/RemoteApp Generator) | RDP or RemoteApp client      | Shortcut                                                                       | Enter the environment without going through the portal |

> 📘 How to choose the method
>
> Use RemoteApp when the user works on Windows and you want the best integration. Use HTML5 when the device is not Windows or you do not want to install a client. Use the direct connection when you prefer direct access, without a portal.

For example: a salesperson with a MacBook connects via HTML5 from the browser, while an office worker with Windows uses RemoteApp to have their ERP integrated into the local desktop.

### Access to the environment

| Way to connect    | How                                                      | When                               |
| ----------------- | -------------------------------------------------------- | ---------------------------------- |
| User portal       | From the browser, with the portal URL and credentials    | Usual everyday access              |
| Direct connection | With an RDP or RemoteApp connection generated previously | When you want to bypass the portal |

### Permissions

Permissions define how much the user can interact with the system. Keep the minimum level each one needs.

| Permission    | Scope                                                                                                       |
| ------------- | ----------------------------------------------------------------------------------------------------------- |
| User          | Works with their applications and their desktop                                                             |
| Administrator | Windows administrator permissions in the environment (install software, change settings, manage the server) |

> #### 🚧 Limit the Administrator role
>
> The Administrator permission gives control over the system. Assign it only to the person who manages the environment, not to regular users, to reduce risk.

### Best practices

* Define the mode and the method with the user's device and what they need to see in mind, not by default.
* Decide printing at the same time as the connection method, because it conditions the available options. You have it in [Printing.](https://docs.plenit.com/docs-en/productos/remote-desktop/details/printing.md)
* Reserve the Administrator permission for whoever administers, not for whoever only works.


---

# 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/details/connection-modes-compatibility.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.
