> 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/intermediate-concepts/variables.md).

# Variables

Las variables de Devolutions Server son marcadores de posición en tiempo de ejecución para credenciales o rutas, lo que permite a Remote Desktop Manager reutilizar valores sin codificar secretos de fo

Las variables en la plataforma Devolutions son marcadores de posición que se resuelven en tiempo de ejecución para que pueda reutilizar valores sin codificarlos de forma fija. Ejemplos habituales incluyen hacer referencia a una entrada de credenciales, a un nombre de usuario o a una ruta específica de un entorno dentro de una línea de comandos o un script.

Devolutions Server almacena los datos subyacentes, mientras que los clientes como Remote Desktop Manager expanden las variables al iniciar una sesión o ejecutar una herramienta. El uso de variables evita copiar secretos en muchos lugares, simplifica la rotación de contraseñas y permite que la misma entrada funcione en varios entornos.

#### Véase también

* [Variables](https://docs.devolutions.net/rdm/es/concepts/intermediate-concepts/variables)


---

# 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/intermediate-concepts/variables.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.