> 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/knowledge-base/how-to-articles/set-a-default-documentation-template-for-a-vault.md).

# Set a default documentation template for a vault

Set a default documentation template for a vault in Remote Desktop Manager so new entries automatically use consistent content.

Learn how to set a default documentation template for all entries in a vault.

1. Open Remote Desktop Manager.
2. In the navigation pane, right-click the vault name at the top of the tree, then select ***Properties***.
3. In the left menu, click ***Documentation***.
4. Select ***Manage templates*** and create a template with the content you want. Save and close.
5. Back in ***Documentation***, set ***Default template*** to ***Custom***.
6. In ***Template*** (on the right), choose the template you created.
7. Enter the ***Documentation title*** (e.g., Windjammer documentation) and select a ***Documentation type***.
8. Select ***Save***.
9. Select an entry.
10. Go to the **Documentation** tab to view the template you previously created.

### See also

* [Devolutions Academy – Predefine a documentation template for all new entries in 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/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.