> 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/create-and-configure-a-project.md).

# Create and configure a project

Create the project around an operating purpose and delivery contract, not around a temporary file type. Modality-specific behavior is loaded by the Workbench from the attached data.

### Before you make the change

* Name the business or model outcome and accountable project owner.
* Identify the published dataset version, ontology owner, workflow owner, and reviewer role.
* Define the first release acceptance criteria.

![Projects list used to start a new project](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)

*Use a naming convention that distinguishes program, environment, or controlled period without relying on a modality label.*

### Understand the product behavior

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.

### Project creation flow

1. The user selects **New Project**.
2. The user enters the project name.
3. Unitlab creates the project and binds the default workflow.
4. The project opens on its **Datasets** page.
5. The user uploads new data or attaches a published dataset version.
6. Each incoming resource is detected as Image, Video, Audio, Text, Medical, or Document.
7. The workflow creates work-item state and routes the item from Project into Annotate or a configured Model stage.
8. If the project has no Live ontology, the user can create/import one centrally or let the first annotation-side Quick Create Class lazily create the initial project ontology.

Project creation does not create an empty data folder, dataset, class, or ontology. Those objects appear when the user first performs the relevant action.

### Establish the project boundary

{% stepper %}
{% step %}

#### 1. Create the project

Give it a durable, purpose-oriented name and clear description.
{% endstep %}

{% step %}

#### 2. Assign ownership

Add the minimum administrators and project operators required for setup.
{% endstep %}

{% step %}

#### 3. Attach the source

Select the explicit dataset version and reconcile created Project Data.
{% endstep %}

{% step %}

#### 4. Add Instructions and ontology

Make the human guidance and structured schema express the same policy.
{% endstep %}

{% step %}

#### 5. Build the workflow

Connect stages, queues, assignment, review, rejection, escalation, and completion.
{% endstep %}

{% step %}

#### 6. Run a calibration cohort

Open representative items in each relevant editor before production assignment.
{% endstep %}
{% endstepper %}

### Decisions that affect production

| Decision      | Production guidance                                                                              |
| ------------- | ------------------------------------------------------------------------------------------------ |
| Project scope | One project should have a coherent policy, workflow, ownership model, and release contract.      |
| Modality      | Do not encode type in the project model; let attached data select the editor.                    |
| Ownership     | Separate platform administration, policy ownership, operations, review, and downstream approval. |
| Scale gate    | Do not assign full volume until the calibration cohort passes review.                            |

### Continue the operating flow

* Complete Project Instructions.
* Inspect Project Data and filter presets.
* Confirm workflow and queue behavior for every role.