> For the complete documentation index, see [llms.txt](https://docs.devolutions.net/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.devolutions.net/rdm/knowledge-base/how-to-articles/configure-anydesk-entry.md).

# Configure AnyDesk entry

Configure an AnyDesk entry in Remote Desktop Manager to remotely access devices with file transfer and session recording features.

AnyDesk entries allows users to access devices remotely on a range of operating systems, notably Windows, MacOS, Linux, Android, and iOS. By leveraging this integration, users benefit from all the features of AnyDesk, including file transfer, remote printing, session recording, integrated collaboration tools, and more.

To create an AnyDesk entry, right-click in the navigation pane and select ***New entry*** or click on the ***New entry*** button located in the content area (***+*** icon). Then, head over to the ***Session*** section, and select the ***AnyDesk*** entry under ***Remote connections***.

This straightforward entry has only a few required fields. First, enter a ***Name***, then specify the ***Host***, which can also be selected from the domain’s computer list by clicking on the ellipsis button (***...***) next to the field, and enter a strong ***Password***. Click on ***Add***.


---

# 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.devolutions.net/rdm/knowledge-base/how-to-articles/configure-anydesk-entry.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.