# Workspaces and projects

A workspace groups projects and provides a shared membership, billing, and storage scope. A project holds the images, annotations, classes, versions, and files for a dataset.

## Create and open a project

1. Open [Workspaces](/workspaces).
2. Select a workspace you can access.
3. Create a project, or open an existing project card.
4. Use the project's settings to upload data, create dataset versions, and inspect files or model runs.

The available actions depend on your workspace role, project role, additional permissions, and image assignments. Seeing a project does not necessarily grant permission to change or delete all its data.

## Organize a review queue

![Demo data · Project image grid with generated sample images](/docs-assets/dataset-grid.jpg)

Demo data · The real project interface with sample records.

Think of the image grid as your team's workbench. Open an image to annotate it, or narrow the grid to a specific question: Which images still need review? Where does a particular class appear? Which batch did a teammate upload?

Use the project's available filters to narrow the data by class, tag, split, filename, verification, or assignment. Confirm the current filter before selecting images for an operation or building a version.

Keep class names consistent across the project. Rename or remove a class through class management rather than editing individual labels merely to simulate a project-wide rename.

### A practical project structure

Create separate projects when the data has a different purpose, ownership, or annotation policy. Within one project, use tags, batches, assignments, and splits to organize related examples instead of creating a new project for every small upload.

For example, an inspection project can contain several camera batches and defect classes. A reviewer can filter one batch, check its annotations, and then create a dataset version from the intended selection.

### Expected result

After setup, your team should have one agreed project, recognizable class names, and a clear way to find the next images to label. The project can grow without requiring you to finish every annotation before starting a review.

## Work with a team

Workspace administrators can manage membership through the workspace controls. Project and image assignments determine which work a collaborator can access. A shared link does not replace membership or permission checks.

Use assignments to divide work, then verification filters to review it. When someone else changes an image or its labels, refresh before replacing your local work. Keep a copy of a draft if a conflict requires you to reload.

## Clone or remove a project

Cloning is a background workflow. Wait for the target to become ready before using it; a timeout while waiting does not mean you should submit another clone.

Project deletion is destructive and may require background cleanup. Protected artifacts can survive project deletion in the account library. Check the files you need before deleting a project, and inspect any cleanup error rather than repeatedly issuing delete requests.

Continue with [Upload data](/docs/upload-data) or [Artifacts and inference](/docs/artifacts-inference).