Workspace · Updated 2026-08-25

Manage Projects, Brand Kits, and reusable Assets

Understand projects, Brand Kits, the cross-document Asset Library, archiving, and safe deletion in Retake Design.

Quick answer

Understand the boundary before taking action.

Projects, Brand Kits, and Assets are connected without becoming duplicate document systems. Projects own editable documents, Brand Kits reference approved identity choices, and the Asset Library adds reusable metadata around one stored image.

  1. 01Projects hold your private designs
  2. 02Assets keep bytes and metadata separate
  3. 03Brand Kits are bounded inputs
  4. 04Deletion follows references

Projects hold your private designs

Home and Projects show work tied to the signed-in account and workspace. Opening a project enters its layered Canvas and loads one DesignDocument authority. Archiving or moving a project to trash changes workspace metadata; it does not silently rewrite the document snapshot.

Assets keep bytes and metadata separate

Imported and generated image bytes enter the Asset repository before an ImageLayer can reference them. The Asset Library records role, tags, source and license facts, and archive state around that same Asset instead of copying the image for each project.

Brand Kits are bounded inputs

A Brand Kit owns palette, typography, voice, prohibited terms, and a stable logo Asset reference. Applying a kit creates a checkpoint and one document-command batch. Agent requests receive an immutable snapshot rather than permission to mutate the kit.

Deletion follows references

Hide or archive is reversible. Permanent deletion is available only after Retake checks current projects, named Versions, and Brand Kits for references. Remove those references deliberately before deleting the shared Asset.

FAQ

Common questions about this path.

Does using one Asset in two projects duplicate its bytes?

No. Cross-document metadata references the same stored Asset record; projects keep references inside their own DesignDocument snapshots.

What happens when I archive an Asset?

It leaves normal library browsing but remains available to documents that already reference it. Archiving is reversible and does not break project rendering.