> 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/es/concepts/basic-concepts/remote-connection-management.md). # Gestión de conexiones remotas La gestión de conexiones remotas en Devolutions Server centraliza las sesiones RDP, SSH y web iniciadas a través de Devolutions Launcher o Remote Desktop Manager. La gestión de conexiones remotas en Devolutions Server centraliza las definiciones de sesión y las inicia a través de Devolutions Launcher o Remote Desktop Manager. Las entradas representan sesiones RDP, SSH, web y de otros tipos, y se pueden abrir desde la interfaz web o desde las herramientas cliente, de modo que los parámetros de conexión y las credenciales permanecen bajo control administrativo. Combinado con funciones como la grabación de sesiones y la integración con Devolutions Gateway, esto proporciona una única vía auditada hacia la infraestructura crítica en lugar de conexiones directas improvisadas. Un equipo de operaciones puede, por ejemplo, abrir todas las sesiones RDP de un cliente desde el navegador, con cada conexión iniciada a través de Devolutions Gateway y registrada de vuelta en Devolutions Server. #### Temas relacionados * [Descripción general de la interfaz web de Devolutions Server](/server/es/web-interface/devolutions-server-web-interface-overview.md) * [Sincronización de Devolutions Launcher y Devolutions Server](https://docs.devolutions.net/launcher/es/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/es/concepts/basic-concepts/remote-connection-management.md?ask=&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.