> 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/concepts/intermediate-concepts/inheritance.md). # Inheritance Inheritance in Devolutions Server lets entries and folders automatically receive permissions and settings from their parent vault or folder. Inheritance in Devolutions Server is the mechanism by which entries and folders automatically receive security and settings from their parents. Typical inherited items include permissions, roles, and certain connection properties defined at the vault or folder level. By designing a clear folder structure and applying rights to groups at higher levels, administrators minimize one off configurations and reduce the risk of misaligned access. For example, you can grant a support team read only access on a top level customer folder and let all child entries inherit that rule, while still overriding inheritance on a sensitive subfolder when stricter controls are required. #### Related topics * [User groups based security](/server/web-interface/user-group-based-security.md) * [Vault access in Devolutions Server](/server/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/concepts/intermediate-concepts/inheritance.md?ask=&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.