For the complete documentation index, see llms.txt. This page is also available as Markdown.

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.

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.

  • Reserve the Administrator permission for whoever administers, not for whoever only works.

Last updated

Was this helpful?