> 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/concepts/intermediate-concepts/inheritance.md). # Inheritance Devolutions Cloud inheritance lets entries and users automatically receive permissions and settings from higher level vaults, folders, and roles. Inheritance is the mechanism that lets entries and users automatically receive settings or permissions from higher level objects instead of redefining them each time. Typical inherited items include permissions, default credentials, and gateway or host settings, which reduce configuration drift and keep security consistent. In Devolutions Cloud, system permissions and roles define baseline rights at system and vault levels, while entries and folders can refine or restrict them. Administrators can review effective access in the Permissions views and adjust roles or explicit overrides when a specific team or privileged account needs tighter control. #### Related topics * [Permissions](/cloud/web-interface/entries/entry-section/permissions.md) * [Assign roles and permissions](/cloud/knowledge-base/how-to-articles/assign-roles-and-permissions.md) * [System permissions](/cloud/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/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.