> 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/es/concepts/intermediate-concepts/inheritance.md). # Herencia La herencia de Devolutions Cloud permite que las entradas y los usuarios reciban automáticamente permisos y configuraciones de bóvedas, carpetas y roles de nivel superior. La herencia es el mecanismo que permite que las entradas y los usuarios reciban automáticamente configuraciones o permisos de objetos de nivel superior en lugar de tener que redefinirlos cada vez. Entre los elementos heredados habituales se incluyen los permisos, las credenciales predeterminadas y la configuración de gateway o de host, lo que reduce la desviación de la configuración y mantiene la coherencia de la seguridad. En Devolutions Cloud, los permisos del sistema y los roles definen los derechos básicos en los niveles de sistema y de bóveda, mientras que las entradas y las carpetas pueden refinarlos o restringirlos. Los administradores pueden revisar el acceso efectivo en las vistas de Permisos y ajustar los roles o las anulaciones explícitas cuando un equipo concreto o una cuenta privilegiada necesita un control más estricto. #### Temas relacionados * [Permisos](/cloud/es/web-interface/entries/entry-section/permissions.md) * [Asignar roles y permisos](/cloud/es/knowledge-base/how-to-articles/assign-roles-and-permissions.md) * [Permisos del sistema](/cloud/es/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/es/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.