> 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/da/web-interface/administration/templates/entry-templates.md).

# Postskabeloner

Administrer postskabeloner i Devolutions Server for at foruddefinere, hvordan nye poster udfyldes, herunder oprettelse af skabeloner fra bunden eller ud fra eksisterende poster.

Med ***Postskabeloner*** kan administratorer administrere postskabeloner i Devolutions Server for brugerne. Med funktionen kan der angives præferencer for, hvordan oplysninger i poster udfyldes, når de oprettes.

For at oprette en ny postskabelon gås der til ***Administration – Postskabeloner***, og der klikkes på knappen ***Tilføj*** eller på duplikerknappen for at kopiere fra en eksisterende skabelon.

Det er også muligt at gemme poster som skabeloner for at bruge deres egenskaber i andre poster. Vælg den post, der skal fungere som model, og klik på menuen ***Mere*** for at få adgang til funktionen ***Gem som skabelon***.

#### Se også

* [Devolutions Academy – Oprettelse af postskabeloner og adgangskodepolitikker](https://academy.devolutions.net/student/path/2942210/activity/4493534)


---

# 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/da/web-interface/administration/templates/entry-templates.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.