> 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/how-to-articles/sealed-entries.md).

# Sealed entries

Seal entries in Remote Desktop Manager to protect sensitive data from higher privileged users and alert administrators of access attempts.

Sealed entries protect sensitive information from being accessed by users with higher privileges and can be used in case of emergency. When an attempt is made to access a sealed entry, the system displays a confirmation message to the user, indicating that the entry is protected. Additionally, a notification is sent to the administrators, alerting them of the access attempt.

{% hint style="info" %}
The sealed entry must be created in a [Devolutions Server workspace](/rdm/concepts/basic-concepts/workspaces.md).
{% endhint %}

### Sealing the entry

1. Go to the entry properties.
2. Click ***Security Settings***.
3. Select ***Sealed*** under ***Seal–State***.
4. Click ***Update*** to save.

### Access Attempts

Unseal an entry sends a notification to the administrators, providing details about the access attempt. This includes the identity of the user attempting access, the time and date of the attempt, and the name of the vault.

### Devolutions Server REST API and sealed entries

Details of an entry can be retrieved through the REST API. Devolutions Server will respond with a sealed entry error message if anyone attempts to access a sealed entry programmatically.

#### See also

* [Devolutions Blog - Spotlight on layered protection with sealed entries](https://blog.devolutions.net/2024/07/inside-20242-layered-protection-with-sealed-entries/)


---

# 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/how-to-articles/sealed-entries.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.