> 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/intermediate-concepts/host-linking-and-host-management.md).

# Host linking and host management

Devolutions Cloud host linking centralizes hostnames, ports, and gateways into reusable entries shared across RDP and SSH sessions.

Host linking and host management centralize common connection settings into reusable host entries so multiple sessions share the same target system definition. Instead of repeating hostnames, ports, and gateways on every RDP or SSH entry, those sessions are linked to a single host entry whose configuration is managed once.

When Remote Desktop Manager uses Devolutions Cloud as a workspace, these host entries live in Devolutions Cloud vaults while launch options are handled by Remote Desktop Manager. This lets you maintain a clean host inventory with auditing, offline cache, and permissions in Devolutions Cloud, while still benefiting from host based dashboards and remote management tools in Remote Desktop Manager.

#### Related topics

* [Host linking and host management](https://docs.devolutions.net/rdm/concepts/intermediate-concepts/host-linking-and-host-management)


---

# 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/intermediate-concepts/host-linking-and-host-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.