> For the complete documentation index, see [llms.txt](https://docs.unitlab.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.unitlab.ai/documentation/projects/projects-overview.md).

# Projects overview

A Unitlab project connects source membership, Instructions, ontology, workflow stages, queues, annotation, review, issues, statistics, settings, and releases. Projects are typeless so the same operating model can support current and future modalities.

{% hint style="info" %}
**Use this area when:** you need to turn reusable data into assigned, governed, reviewable production work.
{% endhint %}

### How this area fits into production

```mermaid
flowchart TB
  A["Project"]
  B["Data"]
  C["Instructions + ontology"]
  D["Workflow + queues"]
  E["Workbench + review"]
  F["Release"]
  A --> B
  A --> C
  A --> D
  B --> E
  C --> E
  D --> E
  E --> F
```

![Unitlab Projects overview](https://292810646-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FGjVLUz4wthGkGlRKM6rM%2Fuploads%2FOJlS4AoR0WSh2nHAeEDJ%2Fprojects-overview.png?alt=media\&token=cbc0a0a6-0c64-4bfd-a222-43d71439c575)

*The project list is the administrative entry point; the project itself contains the controls that determine how data becomes reviewed output.*

### What this area controls

### Projects are typeless

A project is a container for annotation work, not a single-modality project type. New project creation asks for a name only. The creation modal may display informational chips for Image, Video, Audio, Text, Medical, and Document, but those chips are not selectable and do not constrain the project.

The resource establishes its own family during upload. A single project can therefore contain image, video, audio, text, medical, and PDF/document resources side by side. When the user opens an item, Unitlab selects the correct native editor from that item’s family and the active ontology’s markup capabilities.

Projects are typeless containers. A project can be used for a specific modality or combine several modalities, and the editor is selected from each resource’s data family rather than from a fixed project type.

### Start with the right page

| Decision          | Production guidance                                 |
| ----------------- | --------------------------------------------------- |
| Start a program   | Create and configure the project.                   |
| Bring in work     | Add project data from a published dataset version.  |
| Define policy     | Write Project Instructions and attach the ontology. |
| Inspect readiness | Use Project Data QA before assignment.              |
| Change operations | Review Project settings and lifecycle impact first. |

### Operating boundary

* Projects reference durable data; they do not replace Data Space.
* Workflow state belongs to project work, not the source asset lifecycle.
* A release is a deliberate frozen output, not simply the current project view.

### A production-ready handoff

A project is ready when its owners, source versions, Instructions, ontology, workflow, queues, review path, and release contract are all explicit.