Assets
Workspace Assets are the reusable design and reference files for a project — logos, favicons, icons, hero and OG images, brand kits, reference documents, and sample datasets. The app-generation AI can reuse them across every app you build in the project, and you reference them in a generation prompt with an @token.
By the end of this page you will be able to upload an asset, reference it in chat, and manage the assets in your project.
Prerequisites
- Admin or Developer role to add or change assets. Viewers can browse.
- Open Data Vault → Assets.
Assets vs Documents — Documents is a general file store your agents read from. Assets is specifically for design and reference material the app-generation AI reuses when it builds apps. If you want the AI to reuse your logo or a sample dataset, put it here.
Upload an asset
Open the upload dialog
Click Upload asset. The New workspace asset dialog opens.
Add the file and details
Drop a file (up to 25 MB) or browse, then fill in:
- Display name (required).
- Role (required) — what kind of asset it is: Logo, Favicon, Image, Icon, OG Image, Reference Document, Sample Data, or Other.
- Mention token — the
@tokenused to reference the asset in chat. Leave it blank to derive one from the display name. - Usage notes (helps the AI) — a short note telling the AI when and how to use this asset.
Save
Click Save asset. It appears in the grid with its role badge and mention token.
Logo, Favicon, and OG Image are singletons — a project has at most one of each. Uploading a second of the same role replaces the first.
Reference an asset in chat
Each asset card has a copyable @token chip. In a generation prompt, type @ to pick an asset, or paste its token — for example, “use @company-logo in the header”. The AI resolves the token to the asset and reuses the file when it builds or updates the app.
Manage assets
- Search — filter the grid by name, token, role, or usage notes.
- From a card’s ⋮ menu: Preview, Edit metadata (display name, role, mention token, usage notes), Replace file (swap the underlying file, keeping the metadata), or Delete.
Deleting an asset removes it from the project, but apps you already built keep their own bundled copy — deleting doesn’t reach back into shipped apps.
Common issues
- Upload rejected — the file is over the 25 MB limit.
- Can’t add a second logo/favicon/OG image — those roles are singletons; edit or replace the existing one instead.
- The AI didn’t use an asset — reference its
@tokenexplicitly in your prompt, and add Usage notes so the AI knows when to apply it.
Next
- Generate an app with Vibe Code — where the AI reuses your assets.