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

# Remote connection management

Remote connection management in Devolutions Server centralizes RDP, SSH, and web sessions launched through Devolutions Launcher or Remote Desktop Manager.

Remote connection management in Devolutions Server centralizes session definitions and launches them through Devolutions Launcher or Remote Desktop Manager. Entries represent RDP, SSH, web, and other session types, and can be opened from the web interface or client tools so that connection parameters and credentials remain under administrative control. Combined with features like session recording and integration with Devolutions Gateway, this provides a single audited path into critical infrastructure instead of ad hoc direct connections.

An operations team can, for example, open all RDP sessions for a customer from the browser, with every connection launched via Devolutions Gateway and logged back into Devolutions Server.

#### Related topics

* [Devolutions Server web interface overview](/server/web-interface/devolutions-server-web-interface-overview.md)
* [Devolutions Launcher and Devolutions Server synchronization](https://docs.devolutions.net/launcher/configuration-and-settings/devolutions-launcher-and-devolutions-server-synchronization)


---

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