> 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/knowledge-base-articles/templates-default-path.md).

# Templates default path

Set the default templates path in Remote Desktop Manager and choose between local, shared, or database templates to standardize settings across users.

When creating new entries, the ***Default Settings*** for ***Templates*** are in ***File – Templates – Local Default Settings***.

This is a local setting, which will not be applied to other users of the workspace, nor will it be applied to existing sessions.

The path can be changed by an administrator in the ***System Settings – Paths - Default templates*** to point to a shared drive.

As long as the users have access to the drive, they will have these ***Default Settings***.

That being said, if the users set a ***Default Templates path*** in ***File – Settings – Paths***, it will override the one in ***Administration – System Settings***.

Therefore, if you want to use ***Default Settings*** for multiple users, we would advise using ***Database Templates*** in ***File – Templates – Templates***.

#### See also

* [Devolutions Academy - Creating and Managing Entry Templates](https://academy.devolutions.net/student/path/1925039/activity/2667190)


---

# 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/knowledge-base-articles/templates-default-path.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.