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

# Connection Modes and Permissions

What each user sees, how they connect to the environment (RemoteApp, HTML5, or direct RDP), and what permissions they have.

For each user you define two things: **what they see** when signing in and **how they connect**. To that are added their **permissions**. You configure it in the user profile, within the environment's users section.

### What the user sees

* **Application Launchpad**: the user sees and opens only the applications you publish for them, with no desktop. More focused and lighter.
* **Full desktop**: the user accesses a full Windows desktop, as if it were their work computer.

### How they connect

* **RemoteApp**: the applications run in the environment but integrate with the user's computer almost as if they were local (they can move them between monitors, for example). Designed for Windows PCs. Accessed from the user portal.
* **HTML5**: everything runs inside the web browser. It has somewhat less integration with the local computer, but it is the ideal option for Mac, Linux, or Android. Also from the user portal.
* **Direct connection (RDP or RemoteApp)**: the user connects from their desktop without going through the portal, with a connection generated beforehand (the RDP/RemoteApp Generator). Useful when you prefer direct access to the environment.

<figure><img src="https://3894148717-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FxksPMyYRDCe4qKkhbpcY%2Fuploads%2Fgit-blob-27fd8ba7048cbbd3506f7243d248cea44934e972%2Fdiagram-vias-de-conexion-er.png?alt=media" alt=""><figcaption></figcaption></figure>

> #### 📘 Printing depends on how they connect
>
> Each connection method supports different printing modes.
>
> You see it in [Environment access.](https://docs.plenit.com/docs-en/productos/remote-desktop/concepts/environment-access.md)

### Permissions

* **User**: works with their applications and their desktop.
* **Administrator**: has Windows administrator permissions within the environment, with the control that this entails over the system (install software, change settings, and manage the server).

### How you choose

| User need                                                      | Suitable mode                        |
| -------------------------------------------------------------- | ------------------------------------ |
| Only needs a few specific applications, in Windows             | Launchpad + RemoteApp                |
| Works from Mac, Linux, Android, or without installing anything | HTML5                                |
| Needs the full desktop                                         | Full desktop (RemoteApp or HTML5)    |
| Prefers to enter directly without a portal                     | Direct connection (RDP or RemoteApp) |

### Where to follow

* How to create users and publish their applications: [Users and applications.](https://docs.plenit.com/docs-en/productos/remote-desktop/concepts/users-and-applications.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/connection-modes.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.
