> For the complete documentation index, see [llms.txt](https://documentation.panomics.bio/documentation/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://documentation.panomics.bio/documentation/access-control/ui/children.md).

# Child resource permissions

These are permissions granted directly to this resource that are relevant to its children, and by granting it to this resource, we rely on inheritance to have them have an effect on the resource's children.

## How it works

* Permissions granted here **inherit down** to all children of this resource
* Useful for granting project-wide access to analyses without affecting the project itself
* Enables delegation of management rights to children only

## Special case: `admin` on children

When granting `admin` in this section, it **only applies to the children**, not the parent resource itself.

{% hint style="info" %}
**Children-only admin:** Granting `admin` here applies to **children only**, not the parent. This allows you to delegate full control beneath a resource without elevating the resource itself.
{% endhint %}

## Example use case

You want to give the "Ops-Admins" team full control over all analyses in a project, but not the project itself. You would:

1. Open the **Project → Access → Child Resource Permissions**
2. Add **Ops-Admins** team
3. Set `admin` to **Allow (✔)**

Now Ops-Admins can manage everything under the project, but not the project itself.

{% hint style="info" %}
See the [Admin on children only](https://github.com/panomicsbio/documentation/blob/main/access-control/recipes/admin-children-only.md) recipe for a complete step-by-step guide.
{% endhint %}