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

# Herencia

La herencia en Devolutions Server es el mecanismo mediante el cual las entradas y carpetas reciben automáticamente la seguridad y la configuración de sus elementos principales. Los elementos heredados habituales incluyen permisos, roles y determinadas propiedades de conexión definidas en el nivel de la bóveda o de la carpeta.

Al diseñar una estructura de carpetas clara y aplicar derechos a grupos en niveles superiores, los administradores minimizan las configuraciones puntuales y reducen el riesgo de accesos mal alineados. Por ejemplo, puede conceder a un equipo de soporte acceso de solo lectura en una carpeta de cliente de nivel superior y dejar que todas las entradas secundarias hereden esa regla, y aun así anular la herencia en una subcarpeta sensible cuando se requieran controles más estrictos.

#### Temas relacionados

* [Seguridad basada en grupos de usuarios](/server/es/web-interface/user-group-based-security.md)
* [Acceso a bóvedas en Devolutions Server](/server/es/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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.devolutions.net/server/es/concepts/intermediate-concepts/inheritance.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.