> For the complete documentation index, see [llms.txt](https://academy.shade.inc/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://academy.shade.inc/help-center/help-center-es/drive-faq/que-es-la-herencia-de-unidades.md).

# ¿Qué es la herencia de unidades?

La herencia de la unidad es el permiso predeterminado que una unidad otorga a los miembros del espacio de trabajo. Todo miembro del espacio de trabajo que no se agregue explícitamente a la unidad con un permiso diferente obtiene este valor predeterminado. Por ejemplo, si la herencia de una nueva unidad es **Acceso total**, todo miembro del espacio de trabajo tiene acceso total a ella.

Cualquier administrador de la unidad, o un administrador del espacio de trabajo, puede cambiar la herencia de una unidad. Ve a **Configuración > Unidades > \<nombre de la unidad> > Miembros > Herencia predeterminada**.

![Cambio de la herencia predeterminada de una unidad](https://1866928944-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FlvHrZ4ybpa07fNCxAfwz%2Fuploads%2FdSosTE6UzTa8HPZTBMQW%2Fdrive-default-inheritance.png?alt=media)

Para ver más ejemplos, consulta [Ejemplos de herencia de permisos](https://academy.shade.inc/sharing-and-collaboration/permission-inheritance-examples).


---

# 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://academy.shade.inc/help-center/help-center-es/drive-faq/que-es-la-herencia-de-unidades.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.