> 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-assets.md).

# Data assets

Assets are the durable source resources that Unitlab processes and presents across Data Space, datasets, projects, and releases. Asset operations should preserve traceability to the original source and current dependencies.

### Before you make the change

* Confirm the active lifecycle view: Active, Archived, or Trash.
* Use filters to resolve the exact target set before bulk action.
* Review dataset and project dependencies for any destructive lifecycle change.

![Unitlab Asset library list view](https://292810646-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FGjVLUz4wthGkGlRKM6rM%2Fuploads%2FnjhYnLvSAjgnkvCf8QE9%2Fassets-library.png?alt=media\&token=e0b7397b-0f96-479d-8344-bf8a5f37d02b)

*List view is suited to operational details and bulk work; Grid is suited to visual inspection; Embedding is suited to distribution and similarity questions.*

### Understand the product behavior

The Asset library separates Folders and Assets and provides list, grid, and embedding views. It supports:

* upload;
* search;
* selection and bulk actions;
* list and grid presentation;
* sorting by name, size, modification date, and creator;
* folder organization;
* pagination;
* active, archived, and trash lifecycle states.

Search covers assets, folders, tags, and projects. The current list view makes source, size, modification date, and creator visible, which helps operational teams answer where data came from and who changed it.

Automation supports folder creation, nested subfolders, folder listing, asset upload, asset-level custom metadata, cloud-folder creation, and synchronization.

### Workspace Data Space navigation

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, Delete, 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.

Deleting data that is still attached to projects is a two-phase flow: Unitlab first shows affected projects and requires the relevant source links to be detached. This reduces the risk that a workspace administrator deletes source data without seeing its downstream use.

### Row actions and activity

Folder and asset row actions include Open, Rename, Move, Download, Archive, Tag, Activity, and Delete where the backing supports them. Opening **Activity** replaces the filter sidebar with a read-only, newest-first timeline showing who changed what, when, affected-file counts, and rename/move/metadata differences. Users can search or filter events and download the complete affected-file JSON for a large change.

The activity record remains available after the original subject is permanently deleted. Objects created before activity tracking was enabled can have an empty history because earlier events are not reconstructed.

### Inspect and operate an asset cohort

{% stepper %}
{% step %}

#### 1. Find the cohort

Search or filter by source, type, state, metadata, tag, size, dimensions, or dates.
{% endstep %}

{% step %}

#### 2. Choose the view

Use List for fields and bulk actions, Grid for visual QA, or Embedding for distribution.
{% endstep %}

{% step %}

#### 3. Inspect representative items

Open row activity and the native viewer before changing lifecycle state.
{% endstep %}

{% step %}

#### 4. Apply the intended action

Tag, archive, restore, or trash only the reviewed selection.
{% endstep %}

{% step %}

#### 5. Reconcile dependencies

Confirm expected dataset, project, and release behavior after the change.
{% endstep %}
{% endstepper %}

### Decisions that affect production

| Decision         | Production guidance                                                                                                      |
| ---------------- | ------------------------------------------------------------------------------------------------------------------------ |
| Archive vs trash | Archive removes active operational visibility while retaining recoverable history; trash is a stronger lifecycle action. |
| Bulk scope       | The resolved item count is part of the approval decision.                                                                |
| Evidence         | Record the target filter, count, owner, and reason for material bulk changes.                                            |

### Continue the operating flow

* Curate with metadata and tags.
* Create Data Groups when files must remain together.
* Publish stable membership as a dataset version.