> 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/concepts/basic-concepts/information.md).

# Oplysninger

Oplysningsposter i Devolutions Server gemmer referencedata som procedurer, kontakter eller aktivoplysninger sammen med legitimationsoplysninger og dokumenter.

Oplysningsposter i Devolutions Server er fleksible poster til lagring af referencedata, der ikke er en fjernsession eller en selvstændig legitimationsoplysning, f.eks. procedurer, kontakter eller aktivoplysninger. Posterne findes sammen med andre poster i forretningsorienterede bokse, deler den samme tilladelsesmodel og kan kombineres med dokumenter, vedhæftede filer og brugerdefinerede felter for at opbygge lette vidensartikler. Når De bruger oplysningsposter i stedet for separate wikier, holdes den driftsmæssige kontekst tæt på de adgangskoder og forbindelser, som Deres teams faktisk bruger.

Et typisk brugstilfælde er en oplysningspost, der dokumenterer en server, med links til dens RDP- og SSH-poster plus noter om vedligeholdelsesvinduer.

#### Relaterede emner

* [Poster](/server/da/web-interface/vaults/entries.md)
* [Indholdstyper for bokse](/server/da/web-interface/customization/vault-content-types.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/da/concepts/basic-concepts/information.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.
