> 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/cloud/concepts/basic-concepts/remote-connection-management.md).

# Remote connection management

Devolutions Cloud remote connection management stores RDP, SSH, VNC, and web sessions that you launch securely through Devolutions Gateway and clients.

Remote connection management in Devolutions Cloud lets you store RDP, SSH, VNC, Telnet, and web sessions as entries and launch them securely through Devolutions Gateway and supporting clients. Session-type entries define the target host, protocol, credentials, and optional Devolutions Gateway tunnel so users can open systems directly from the web interface Remote Desktop Manager or Devolutions Launcher.

Centralizing sessions in Devolutions Cloud ensures they inherit vault permissions, are audited, and can be temporarily checked out when combined with privileged access features. For example, an operator can select an RDP entry in a shared operations vault and click Open in web client to reach a production server via Devolutions Gateway without needing a VPN or direct network access.

#### Related topics

* [Entry type](/cloud/web-interface/entries/entry-type.md)
* [Launch a session via the Devolutions Cloud web interface](/cloud/knowledge-base/how-to-articles/launch-a-session-via-the-devolutions-cloud-web-interface.md)


---

# 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/cloud/concepts/basic-concepts/remote-connection-management.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.