> 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/server/da/concepts/intermediate-concepts/inheritance.md).

# Nedarvning

Nedarvning i Devolutions Server lader poster og mapper automatisk modtage tilladelser og indstillinger fra deres overordnede boks eller mappe.

Nedarvning i Devolutions Server er den mekanisme, hvormed poster og mapper automatisk modtager sikkerhed og indstillinger fra deres overordnede elementer. Typiske nedarvede elementer omfatter tilladelser, roller og visse forbindelsesegenskaber, der er defineret på boks- eller mappeniveau.

Ved at designe en tydelig mappestruktur og tildele rettigheder til grupper på højere niveauer minimerer administratorer enkeltstående konfigurationer og mindsker risikoen for forkert tilpasset adgang. De kan for eksempel give et supportteam skrivebeskyttet adgang til en kundemappe på øverste niveau og lade alle underordnede poster nedarve den regel, samtidig med at nedarvningen stadig kan tilsidesættes i en følsom undermappe, når der kræves strengere kontroller.

#### Relaterede emner

* [Sikkerhed baseret på brugergrupper](/server/da/web-interface/user-group-based-security.md)
* [Boksadgang i Devolutions Server](/server/da/web-interface/vault-access-in-devolutions-server.md)


---

# 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/server/da/concepts/intermediate-concepts/inheritance.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.