> 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 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 which device they can work from. For the conceptual framework, go to [Connection modes and permissions.](/docs-en/productos/remote-desktop/concepts/connection-modes.md) ### Mode: what the user sees The mode determines whether the user works with a full desktop or only with their applications. | Mode | What they see | Fits when | | ---------------------- | ------------------------------------------- | --------------------------------------------------------------------------------------- | | Applications Launchpad | Only the published applications, no desktop | The user needs a few specific applications and focused access | | Remote Desktop | A full Windows desktop | The user works as they would on an office PC, with several tools and the desktop itself | ### Connection methods The method determines how the session reaches the user and from which device they can sign in. The key difference is the level of integration with their device and whether they need to install anything. | Method | Access | Devices | Integration with the device | What it solves | | ----------------- | ----------------------------------- | ---------------------------- | ------------------------------------------------------------------------------------------ | ------------------------------------------------------ | | RemoteApp | User portal | Windows | High: the applications 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 direct connection when you prefer direct access, without a portal. For example: a salesperson with a MacBook signs in 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 sign in | How | When | | ----------------- | ------------------------------------------------------- | ---------------------------------- | | User portal | From the browser, with the portal URL and credentials | Regular day-to-day access | | Direct connection | With a previously generated RDP or RemoteApp connection | When you want to bypass the portal | ### Permissions Permissions define how much of the system the user can touch. Keep the minimum level each one needs. | Permission | Scope | | ------------- | ----------------------------------------------------------------------------------------------------------- | | User | Works with their applications and 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 those who manage the environment, not to working users, to reduce risk. ### Best practices * Define the mode and the method based on the user's device and what they need to see, not by default. * Decide printing at the same time as the connection method, because it affects the available options. You have it in [Printing.](/docs-en/productos/remote-desktop/details/printing.md) * Reserve the Administrator permission for the person who manages, not for the person who 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 dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://docs.plenit.com/docs-en/productos/remote-desktop/details/connection-modes-compatibility.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. 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.