> 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/set-a-default-documentation-template-for-a-vault.md).

# Establecer una plantilla de documentación predeterminada para una bóveda

Configure una plantilla de documentación predeterminada para una bóveda en Remote Desktop Manager para que las nuevas entradas usen automáticamente un contenido coherente.

Aprenda a configurar una plantilla de documentación predeterminada para todas las entradas de una bóveda.

1. Abra Remote Desktop Manager.
2. En el panel de navegación, haga clic con el botón derecho en el nombre de la bóveda, en la parte superior del árbol, y seleccione ***Properties***.
3. En el menú de la izquierda, haga clic en ***Documentation***.
4. Seleccione ***Manage templates*** y cree una plantilla con el contenido que desee. Guarde y cierre.
5. De vuelta en ***Documentation***, establezca ***Default template*** en ***Custom***.
6. En ***Template*** (a la derecha), elija la plantilla que ha creado.
7. Introduzca el ***Documentation title*** (por ejemplo, Windjammer documentation) y seleccione un ***Documentation type***.
8. Seleccione ***Save***.
9. Seleccione una entrada.
10. Vaya a la pestaña **Documentation** para ver la plantilla que ha creado anteriormente.

### Véase también

* [Devolutions Academy – Predefinir una plantilla de documentación para todas las entradas nuevas en RDM](https://academy.devolutions.net/student/activity/3123671-predefine-a-documentation-template-for-all-new-entries-in-rdm)


---

# 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/set-a-default-documentation-template-for-a-vault.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.
