> 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/data/data-folders.md).

# Data folders

Organize durable source resources without confusing folders with versions.

Folders create an understandable source library. They are navigation and ownership boundaries—not immutable membership, workflow state, or downstream delivery.

![Data Space folder hierarchy](https://292810646-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FGjVLUz4wthGkGlRKM6rM%2Fuploads%2F2KQcwfm4EbhGeUaipbJa%2Fassets-folders.png?alt=media\&token=3685bc54-6204-4a4e-a918-84c798aac689)

*Use folders to reflect stable source ownership or acquisition structure; use metadata and tags for dimensions that change more frequently.*

Data Space has three separate top-level pages:

* **Assets** — a Folders/Assets tabbed workspace library;
* **Datasets** — the standalone versioned dataset list;
* **Releases** — versioned project annotation snapshots.

The Assets page mirrors active tab and pagination in the URL. Folder detail presents one file-explorer list containing child folders, loose assets, and Data Groups. Breadcrumbs preserve the full path.

The Assets tab shows one source-of-truth row per asset rather than every clone created in every project. Source identity is reused when a published version is attached, so duplicate project copies do not inflate the workspace asset count.

### Lifecycle and bulk actions

Folders, assets, and datasets share three lifecycle views:

* **Active** — available for normal use;
* **Archived** — reversibly set aside;
* **Trash** — recoverable deletion state.

Hard deletion is available only from Trash. Selecting rows opens a floating action bar whose choices adapt to the current lifecycle. Depending on the object and state, actions include Move, Tags, Download, Archive, Unarchive, Restore, Move to Trash, Delete forever, and Attach to project.

For Download, one selected workspace file downloads directly. Multiple selected files produce a manifest of secure file URLs rather than silently building an unbounded archive in the browser.

Moving files or folders to Trash needs no detach step, even while they are used in projects: **Move to Trash** archives their project copies and keeps the annotations, and the confirmation dialog names those projects. **Delete forever**, available in Trash, also deletes those project copies together with their annotations. Only a dataset that is attached to projects keeps a two-phase flow: the dialog lists the affected projects and the dataset must be detached from each one before it can be moved to Trash. This reduces the risk that a workspace administrator deletes source data without seeing its downstream use.

### Use this in production

* Adopt a naming convention that communicates source and ownership without embedding sensitive data.
* Use folder depth sparingly; prefer searchable metadata for changing business dimensions.
* Before moving or archiving content, review dataset and project dependencies.
* Publish a dataset version when a folder-derived cohort must be reproduced.

***

> **Related Unitlab capability guides:** [Unitlab’s data curation platform](https://unitlab.ai/en/data-curation)