> 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/concepts/intermediate-concepts/templates.md). # Templates Devolutions Server templates predefine connection settings, naming conventions, permissions, and documentation to standardize how new entries are created. Templates in Devolutions Server are predefined entry configurations that standardize how new sessions, credentials, and information records are created. A template can define default connection settings, naming conventions, permissions, and even attached documentation so that every new entry of that type starts from the same baseline. Administrators maintain templates in one place and update them as practices evolve, which helps enforce consistency across large teams. For example, you can provide a template for customer VPN entries that always includes the correct gateway settings, folder location, and tag structure. #### Related topics * [Entry templates](/server/web-interface/administration/templates/entry-templates.md) * [Create entries manually](/server/web-interface/vaults/entries/create-entries-manually.md) --- # 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/concepts/intermediate-concepts/templates.md?ask=&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.