> 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/rdm/es/knowledge-base/how-to-articles/configure-a-splashtop-dashboard-entry-in-remote-desktop-manager.md).

# Configurar una entrada de panel de Splashtop en Remote Desktop Manager

Configure una entrada de panel de Splashtop en Remote Desktop Manager mediante un token de API para gestionar y conectarse a los equipos de Splashtop.

La configuración de la entrada de panel de Splashtop en Remote Desktop Manager tiene algunos requisitos.

1. Inicie sesión en su cuenta de [Splashtop](https://my.splashtop.com/signin).
2. Establezca el ***token de API*** haciendo clic en ***Management - Settings***.
3. Vaya a ***API - Create API token***.
4. Establezca un ***Name*** y haga clic en ***Save***. La configuración predeterminada puede permanecer sin cambios.
5. Active el ***token de API***.
6. Vaya a ***Computers - Add Computer***.
7. Haga clic en ***Copy Link*** y péguelo en el navegador de los otros equipos que desee añadir.
8. Descargue e instale el ***Splashtop Streamer*** desde el enlace. Esto debería añadir automáticamente el equipo a su cuenta de Splashtop.
9. Abra Remote Desktop Manager.
10. Cree una [entrada](https://docs.devolutions.net/rdm/es/ribbon-menu-bar/edit/create-an-entry.md).
11. Introduzca su ***Cuenta*** y su ***clave de API***.
12. Haga clic en ***Añadir*** para guardar la entrada.


---

# 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/rdm/es/knowledge-base/how-to-articles/configure-a-splashtop-dashboard-entry-in-remote-desktop-manager.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.
