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

# Nedarvning

Nedarvning i Devolutions Cloud lader poster og brugere automatisk modtage tilladelser og indstillinger fra bokse, mapper og roller på et højere niveau.

Nedarvning er den mekanisme, der lader poster og brugere automatisk modtage indstillinger eller tilladelser fra objekter på et højere niveau i stedet for at definere dem igen hver gang. Typiske nedarvede elementer omfatter tilladelser, standardlegitimationsoplysninger og indstillinger for gateway eller vært, hvilket mindsker konfigurationsafvigelse og holder sikkerheden ensartet.

I Devolutions Cloud definerer systemtilladelser og roller grundlæggende rettigheder på system- og boksniveau, mens poster og mapper kan finjustere eller begrænse dem. Administratorer kan gennemgå den effektive adgang i visningerne Tilladelser og justere roller eller eksplicitte tilsidesættelser, når et bestemt team eller en privilegeret konto har brug for strammere kontrol.

#### Relaterede emner

* [Tilladelser](/cloud/da/web-interface/entries/entry-section/permissions.md)
* [Tildel roller og tilladelser](/cloud/da/knowledge-base/how-to-articles/assign-roles-and-permissions.md)
* [Systemtilladelser](/cloud/da/web-interface/administration/configuration-and-security/system-permissions.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/cloud/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.