> For the complete documentation index, see [llms.txt](https://docs.parallels.com/landing/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.parallels.com/landing/ras-mp-guide/v21-en-us/infrastructure/rd-session-hosts/configure-an-rd-session-host/desktop-access.md).

# Desktop Access

The **Desktop Access** category allows you to restrict remote desktop access to certain users.

To use default settings, select the **Inherit default settings** option. See the **Using default settings** subsection above.

By default, all users who have access to remote applications on an RD Session Host can also connect to the host via a standard RDP connection. If you want to restrict remote desktop access to certain users, do the following:

1. Select the **Restrict direct desktop access to the following users** option. If you have the **Inherit default settings** option selected, click the **Edit Defaults** link to see (and modify if needed) the default configuration. The rest of the steps apply to both the **Host Properties** and **Default Host Properties** dialogs.
2. Click the plus-sign icon.
3. Select the desired users. To include multiple users, separate them by a semicolon.
4. Click **OK**.

Users in this list will still be able to access remote applications using Parallels Client, but will be denied direct remote desktop access to this host.

Please note that members of the Administrator group will still be able to connect to the remote desktop even if they are included in this list.


---

# 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.parallels.com/landing/ras-mp-guide/v21-en-us/infrastructure/rd-session-hosts/configure-an-rd-session-host/desktop-access.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.