> 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

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](https://docs.devolutions.net/rdm/concepts/basic-concepts/workspaces/).
{% endhint %}

### Sealing the entry

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

   <figure><img src="https://cdnweb.devolutions.net/docs/RDMW6006_2024_2.png" alt=""><figcaption></figcaption></figure>
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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.devolutions.net/rdm/knowledge-base/how-to-articles/sealed-entries.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.