> 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/da/knowledge-base/how-to-articles/configure-a-rustdesk-entry-in-remote-desktop-manager.md).

# Konfigurer en RustDesk-post i Remote Desktop Manager

Konfigurer en RustDesk-post i Remote Desktop Manager for at få adgang til open source-værktøjet til fjernskrivebord ved hjælp af dets id og adgangskode.

RustDesk-poster giver brugerne mulighed for problemfrit at få adgang til den selvhostede open source-software til administration af fjernskrivebord direkte i Remote Desktop Manager. Udnyt RustDesk-integrationen i Remote Desktop Manager til sikker fjernstyring uden kompleks udrulning.

For at oprette en RustDesk-post skal De højreklikke i navigationsruden og vælge ***Ny post*** eller klikke på knappen ***Ny post*** i indholdsområdet (ikonet ***+***). Gå derefter til afsnittet ***Session***, og vælg posten ***RustDesk*** under ***Fjernforbindelser***.

Denne enkle post har kun nogle få påkrævede felter. Angiv først et ***Navn***, og angiv derefter ***Id*** og ***Adgangskode*** for Deres RustDesk-klient. Klik på ***Tilføj***.

’


---

# 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/da/knowledge-base/how-to-articles/configure-a-rustdesk-entry-in-remote-desktop-manager.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.