> 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/da/knowledge-base/knowledge-base-articles/entry-settings/insurance-number.md).

# Forsikringsnummer

Konfigurer dataposten Forsikringsnummer i Remote Desktop Manager til at gemme forsikringstype, forsikringstager, selskab, agent, datoer og dækning.

Denne artikel beskriver de indstillinger og valgmuligheder, der er tilgængelige for dataposter ***Forsikringsnummer*** i Remote Desktop Manager.

<table data-header-hidden><thead><tr><th width="200"></th><th></th></tr></thead><tbody><tr><td><strong>INDSTILLINGER</strong></td><td><strong>BESKRIVELSE</strong></td></tr><tr><td><strong>Navn</strong></td><td>Navnet på posten. Dette felt er obligatorisk.</td></tr><tr><td><strong>Mappe</strong></td><td>Den mappe, hvor posten findes.</td></tr><tr><td><strong>Visning</strong></td><td><p>Hvordan posten åbnes:</p><ul><li><strong>Integreret (faner)</strong> — Åbner posten i en fane i hovedvinduet.</li><li><strong>Fradocket</strong> — Åbner posten i et separat vindue. Yderligere lister lader Dem vælge skærmen og det virtuelle skrivebord, hvor vinduet åbnes.</li></ul><p>På Linux indeholder listen også <em><strong>Standard (nedarvet)</strong></em>, som bruger visningstilstanden for den nærmeste overordnede mappe, der angiver en, og ellers standarden for posttypen. Den tilstand, den opløses til, vises ved siden af listen.</p></td></tr></tbody></table>

### Generelt

<table><thead><tr><th width="220">INDSTILLINGER</th><th>BESKRIVELSE</th></tr></thead><tbody><tr><td><strong>Type</strong></td><td><p>Vælg forsikringstypen:</p><ul><li><strong>Køretøj</strong></li><li><strong>Bolig</strong></li><li><strong>Sundhed</strong></li><li><strong>Liv</strong></li><li><strong>Invaliditet</strong></li><li><strong>Rejse</strong></li><li><strong>Erhverv</strong></li><li><strong>Andet</strong></li></ul></td></tr><tr><td><strong>Forsikringsnummer</strong></td><td>Angiv forsikringsnummeret.</td></tr><tr><td><strong>Forsikringstagers navn</strong></td><td>Angiv forsikringstagerens navn.</td></tr><tr><td><strong>Forsikringsnavn</strong></td><td>Angiv forsikringens navn.</td></tr><tr><td><strong>Virksomhed</strong></td><td>Vælg en kontaktpost for forsikringsselskabet, eller skriv et navn.</td></tr><tr><td><strong>Leveringsdato</strong></td><td>Vælg forsikringens leveringsdato. Når der ikke er angivet en dato, viser feltet den aktuelle dato.</td></tr><tr><td><strong>Slutdato</strong></td><td>Vælg den dato, forsikringen slutter. Når der ikke er angivet en dato, viser feltet den aktuelle dato.</td></tr><tr><td><strong>Forsikringsagentens navn</strong></td><td>Vælg en kontaktpost for forsikringsagenten, eller skriv et navn.</td></tr><tr><td><strong>Dækningsbeløb</strong></td><td>Angiv det beløb, forsikringen dækker.</td></tr></tbody></table>


---

# 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/da/knowledge-base/knowledge-base-articles/entry-settings/insurance-number.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.