> 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/concepts/resources-hierarchy.md).

# Resources & hierarchy

Access in Panomics is granted to principals (Users, Teams) on specific resources and enforced for those principals at the resource level. Resources have the option to edit access in their detailed view.

## Available resources

Resources with editable access currently include:

* **Organization** - With a special edit space in each team's details
* **Project** - Contains analyses and assets
* **Analysis** - Individual computational workflows
* **Bio-Apps** - Reusable analysis applications

## Hierarchy example

**Organization → Project → Analysis**

## Access inheritance

Resources in Panomics have a parent-child relationship (e.g., Project → Analysis). This enables you to define access rules at the parent level that apply to all children.

**Use Case Example:**

You want the "Biologists" team to have access to view all project information on Project A, but also access to view results and run commands in all analyses (present and future) that exist as part of Project A. You achieve this by granting analysis access actions to this team at the **Project level** → which are then inherited automatically to all its Analysis children.

{% hint style="info" %}
Grants on a **parent** can **inherit** to its **children**. Fine-tune with **Direct** and **Deny** at lower levels using the [Resource Access Window](/documentation/access-control/ui.md).
{% endhint %}


---

# 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://documentation.panomics.bio/documentation/access-control/concepts/resources-hierarchy.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.