> 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/password-manager/it/application/launch-a-session-from-devolutions-password-manager-on-desktop.md).

# Avviare una sessione da Devolutions Password Manager su desktop

Avvii sessioni remote da Devolutions Password Manager su desktop tramite Remote Desktop Manager o Devolutions Launcher, oppure apra le voci con un doppio clic.

Avvii una sessione in Remote Desktop Manager o in Devolutions Launcher tramite l'interfaccia utente, oppure ottimizzi il processo dovendo solo fare doppio clic su una voce per avviarla.

### Avvio tramite l'interfaccia utente

Selezioni la voce desiderata e clicchi su ***Apri in RDM*** o ***Apri in Launcher***.

### Avvio tramite un doppio clic

1. In Devolutions Password Manager, clicchi su ***File*** – ***Impostazioni*** – ***Voci***.
2. Abiliti l'opzione ***Apri connessione*** e scelga tra Remote Desktop Manager e Devolutions Launcher.
3. Clicchi sulla ***X*** per chiudere il menu delle opzioni.
4. Torni a una cassaforte e faccia doppio clic su una voce per avviarla tramite l'applicazione precedentemente scelta.


---

# 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/password-manager/it/application/launch-a-session-from-devolutions-password-manager-on-desktop.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.