> 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/environment-access.md).

# Environment Access

Your users enter the environment from any site and device. Here you can see where they enter from and how you protect that access.

### The gateway

* **User portal**: the usual route. The user signs in with their credentials and accesses their applications or their desktop, via RemoteApp or HTML5 depending on their device.
* **Direct RDP connection**: to sign in from the user's desktop with an RDP client, without going through the portal.

The details of each route are in [Connection modes and permissions.](/docs-en/productos/remote-desktop/concepts/connection-modes.md)

### Secure access

* **2FA**: you enable two-step verification per user, so sign-in does not depend only on the password.
* **VPN**: you connect the environment privately, with remote access VPN (for users) and site-to-site (to join the client's network with the environment). It follows the same network model as Servers.
* **Ports and firewall**: you define what remains accessible for access to the environment from the associated Servers subscription.

> #### 📘 Decide how the environment is exposed
>
> Combine portal, VPN, and port rules depending on how exposed you want the environment to be. The more closed the access, the smaller the exposed surface.

### Printing

Printing from a remote environment supports several methods, mainly **Universal Printer**, **TS Print** and **printer mapping**. Which one you can use depends on the user's connection mode (RemoteApp, HTML5, or direct connection), so it's best to decide printing and connection mode together.

### Where to continue

* Configure 2FA, VPN, ports, and printing [(TS Print, local printers)](/docs-en/support/tutorials/windows/tsprint-basic-configuration.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 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/concepts/environment-access.md?ask=<question>&goal=<endgoal>
```

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