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

# Insurance number

Configure the Insurance number data entry in Remote Desktop Manager to store the insurance type, policy holder, company, agent, dates, and coverage.

This article details the settings and options available for ***Insurance number*** data entries in Remote Desktop Manager.

<table data-header-hidden><thead><tr><th width="200"></th><th></th></tr></thead><tbody><tr><td><strong>SETTINGS</strong></td><td><strong>DESCRIPTION</strong></td></tr><tr><td><strong>Name</strong></td><td>The name of the entry. This field is required.</td></tr><tr><td><strong>Folder</strong></td><td>The folder where the entry is located.</td></tr><tr><td><strong>Display</strong></td><td><p>How the entry opens:</p><ul><li><strong>Embedded (tabbed)</strong> — Opens the entry in a tab of the main window.</li><li><strong>Undocked</strong> — Opens the entry in a separate window. Additional lists let you choose the monitor and the virtual desktop where the window opens.</li></ul><p>On Linux, the list also offers <em><strong>Default (inherited)</strong></em>, which uses the display mode of the nearest parent folder that sets one, otherwise the default of the entry type. The mode it resolves to is shown next to the list.</p></td></tr></tbody></table>

### General

<table><thead><tr><th width="220">SETTINGS</th><th>DESCRIPTION</th></tr></thead><tbody><tr><td><strong>Type</strong></td><td><p>Select the type of insurance:</p><ul><li><strong>Vehicle</strong></li><li><strong>Home</strong></li><li><strong>Health</strong></li><li><strong>Life</strong></li><li><strong>Disability</strong></li><li><strong>Travel</strong></li><li><strong>Business</strong></li><li><strong>Other</strong></li></ul></td></tr><tr><td><strong>Insurance number</strong></td><td>Enter the insurance number.</td></tr><tr><td><strong>Policy holder name</strong></td><td>Enter the name of the policy holder.</td></tr><tr><td><strong>Insurance Name</strong></td><td>Enter the name of the insurance.</td></tr><tr><td><strong>Company</strong></td><td>Select a contact entry for the insurance company, or type a name.</td></tr><tr><td><strong>Delivery date</strong></td><td>Select the delivery date of the insurance. When no date is set, the field shows the current date.</td></tr><tr><td><strong>End date</strong></td><td>Select the date the insurance ends. When no date is set, the field shows the current date.</td></tr><tr><td><strong>Insurance agent name</strong></td><td>Select a contact entry for the insurance agent, or type a name.</td></tr><tr><td><strong>Coverage amount</strong></td><td>Enter the amount covered by the insurance.</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/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.
