> For the complete documentation index, see [llms.txt](https://help.bioinsight.illumina.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.bioinsight.illumina.com/correlation-engine/managing-my-data-in-correlation-engine/managing-data.md).

# Overview

Correlation Engine organises your private and shared data in a hierarchy of **projects**, **studies**, **biosets**, and **groups**. Understanding this structure helps you keep your data organised and control who can see and use it.

## Data Hierarchy

```
Project
└── Study
    ├── Bioset 1
    ├── Bioset 2
    └── Bioset N
```

| Level       | Description                                                                                                         |
| ----------- | ------------------------------------------------------------------------------------------------------------------- |
| **Project** | A container that groups related studies. Used for organising work by experiment, programme, or team.                |
| **Study**   | A collection of one or more biosets derived from the same experiment or dataset.                                    |
| **Bioset**  | A single ranked list of genomic features with associated statistics (e.g., one differential expression comparison). |
| **Group**   | A user-defined collection of users for sharing studies and collaborating.                                           |

For detailed information on each level, see the pages in this section:

* [Projects, Studies, and Groups](/correlation-engine/managing-my-data-in-correlation-engine/projects-studies-groups.md) — Creating, editing, sharing, and deleting data objects.
* [Public and Domain Libraries](/correlation-engine/managing-my-data-in-correlation-engine/libraries.md) — Understanding the two classes of content in CE.


---

# 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://help.bioinsight.illumina.com/correlation-engine/managing-my-data-in-correlation-engine/managing-data.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.