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

# Configurare una voce RustDesk in Remote Desktop Manager

Configuri una voce RustDesk in Remote Desktop Manager per accedere allo strumento di desktop remoto open source utilizzando il suo ID e la sua password.

Le voci RustDesk consentono agli utenti di accedere senza interruzioni al software open source e self-hosted di gestione del desktop remoto direttamente in Remote Desktop Manager. Sfrutti l'integrazione RustDesk in Remote Desktop Manager per un controllo remoto sicuro senza distribuzioni complesse.

Per creare una voce RustDesk, faccia clic con il pulsante destro del mouse nel riquadro di navigazione e selezioni ***Nuova voce*** oppure faccia clic sul pulsante ***Nuova voce*** situato nell'area dei contenuti (icona ***+***). Quindi, si rechi nella sezione ***Sessione*** e selezioni la voce ***RustDesk*** sotto ***Connessioni remote***.

Questa semplice voce presenta solo pochi campi obbligatori; inserisca prima un ***Nome***, quindi specifichi l'***ID*** e la ***Password*** del suo client RustDesk. Faccia clic su ***Aggiungi***.

’


---

# 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/it/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.