> 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/ribbon-menu-bar/administration/vault-settings/default-security-for-entries.md).

# Standardsikkerhed for poster

Angiv standardsikkerhedstilladelser, nedarvet, brugerdefineret eller ikke tilladt, for poster under en boks i boksindstillinger i Remote Desktop Manager.

Under ***Administration*** – ***Boksindstillinger*** skal De gå til fanen ***Nedarvede tilladelser*** og derefter ændre rullelisten ***Tilladelse*** til den ønskede indstilling:

* ***Nedarvet***: Giver brugere og roller, der er tildelt en boks, mulighed for at se indholdet af den boks, men hvad de kan gøre med det, afhænger af, hvordan tilladelserne blev angivet på brugerniveau.
* ***Brugerdefineret***: Gør det muligt at vælge bestemte brugere og brugergrupper for hver tilladelse.
* ***Ikke tilladt***: Nægter enhver adgang for alle brugere, også selv om de har fået adgang til boksen. Det kan for eksempel bruges til at angive tilladelserne på mappe- eller postniveau.

For at bekræfte ændringen skal De redigere en post under boksen og gå til afsnittet ***Sikkerhed – Tilladelser***. Alle tilladelser, der er sat til ***Standard***, nedarver værdien fra ***Systemtilladelser*** eller brugeren. Nedarvede værdier vises ved siden af tilladelserne.


---

# 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/ribbon-menu-bar/administration/vault-settings/default-security-for-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.