Dashboard

Assets

Use Assets as the durable catalog for previews, recipes, version history, inputs, Repro Lock metadata, and workflow JSON.

Asset library

The asset library is the dashboard’s durable catalog. Use it when you care about the creative object itself rather than the exact run that produced it.

Search

Find assets by readable name, tags, or workflow context.

Compare

Review versions without losing earlier recipes.

Reuse

Copy IDs or load a saved version back into a pipeline.

Asset detail

Asset detail pages are where the history becomes useful. They combine the preview, version list, recipe fields, metadata, annotations, and sharing actions for one creative object.

Open Assets, choose an asset, then inspect the version metadata before continuing a workflow.

Versions

Every save creates a version. Versions keep edits and experiments traceable, so a strong v1 can remain available even after a more experimental v2 or v3.

Version naming

Use stable asset names for long-running work, and put experiment-specific details in metadata instead of creating many near-duplicate assets.