> 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/alarm-codes.md).

# Alarm codes

Configure the Alarm codes data entry in Remote Desktop Manager to store alarm codes per employee, with employee codes, notes, and masked values.

This article details the many settings and options available for ***Alarm codes*** 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>Add</strong></td><td>Add an alarm code to the list. The <em><strong>Information - Alarm code</strong></em> window opens.</td></tr><tr><td><strong>Edit</strong></td><td>Modify the selected alarm code in the <em><strong>Information - Alarm code</strong></em> window. Double-clicking an alarm code in the list also opens it.</td></tr><tr><td><strong>Delete</strong></td><td>Remove the selected alarm code from the list.</td></tr><tr><td><strong>View</strong></td><td>Open the selected alarm code in read-only mode.</td></tr><tr><td><strong>Search</strong></td><td>Filter the list by name, alarm code, or employee code. A masked alarm code is not matched by its value.</td></tr><tr><td><strong>Name</strong></td><td>The employee the alarm code belongs to.</td></tr><tr><td><strong>Alarm code</strong></td><td>The alarm code. A masked alarm code is hidden in the list.</td></tr><tr><td><strong>Employee code</strong></td><td>The code that identifies the employee.</td></tr></tbody></table>

**Information - Alarm code**

<table><thead><tr><th width="220">SETTINGS</th><th>DESCRIPTION</th></tr></thead><tbody><tr><td><strong>Employee</strong></td><td>Enter the name of the employee the alarm code belongs to. This field is required.</td></tr><tr><td><strong>Alarm code</strong></td><td>Enter the alarm code. This field is required.</td></tr><tr><td><strong>Employee code</strong></td><td>Enter the code that identifies the employee.</td></tr><tr><td><strong>Mask information</strong></td><td>Hide the alarm code in the list. This option is shown only to users allowed to view the alarm code, and not when the alarm code is opened with <em><strong>View</strong></em>.</td></tr><tr><td><strong>Note</strong></td><td>Enter additional information about this alarm code.</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/alarm-codes.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.
