Assets

An asset is a piece of binary content stored in the platform - a logo, a watermark, a custom font. Themes and report templates reference assets by stable URL or by an asset:// reference.

Assets live in Workspace → Assets in the Manager. They are scoped to the workspace, like themes.

What you can store

Anything binary, but in practice:

• Logos and brand imagery (PNG, JPG, SVG).
• Background images and watermarks.
• Custom fonts (WOFF, WOFF2, TTF, OTF) - referenced from themes.
• Signature images for documents.
• Product images if you can't fetch them directly from your data source.

The Manager places per-file size limits (default 25 MB) and per-workspace total limits depending on your plan. Larger workloads should keep heavy media in a CDN and reference it by URL instead of uploading.

Uploading

From Workspace → Assets → Upload, pick one or more files. The upload happens straight to the platform's object store. Each asset gets:

• A filename (the original name).
• A stable URL (used in <image> blocks, theme references, etc.).
• An asset://... reference (used inside the editor when you don't want to hard-code a URL).
• Metadata - content type, size, uploader, date.

Re-uploading a file with the same name replaces the previous version; references using the stable URL or asset:// reference resolve to the latest version. If you need a version-pinned reference, copy the URL from the asset's detail page (it includes a checksum suffix).

Referencing in the editor

Three common ways:

• Image block. Open the block's properties, click "Pick asset", choose from the picker.
• Theme. In the theme editor's typography section, "Add custom font" opens the asset picker and registers the font for the theme.
• Liquid expression. Anywhere a URL is accepted, you can write {{ 'asset://logo.png' | asset_url }} to resolve to a current URL.

Tenancy and access

• Assets are workspace-scoped. A logo.png in Operations is invisible to Finance.
• They are publicly addressable by URL once uploaded. Treat them like CDN content - don't store secrets, internal-only PDFs, or anything that needs row-level access control. Sensitive content should live in a data source, not in the asset store.
• Stable URLs include a workspace identifier and a content hash; they are unguessable for typical workloads but should not be relied on for secrecy.

Lifecycle

• Edit metadata - rename, replace, change description.
• Replace - upload a new file under the same reference; existing reports automatically pick up the new version.
• Delete - if any report or theme references the asset, the Manager warns you and lists the dependants. Deletion goes through soft-delete first; restoration is possible within 30 days.

Best practices

• Optimise before upload. A 10 MB JPEG used as a hero image rendered at 600px wide is wasted weight in every PDF generated. Compress and resize to render dimensions first.
• SVG for logos. Vector logos scale crisply regardless of page size; raster logos pixelate when scaled up.
• Subset fonts. A 5 MB WOFF2 with full glyph coverage is overkill if your reports only use Latin characters. Generate a subset before uploading.
• Use the asset picker, not raw URLs. Pasting a URL works but breaks if the asset is renamed or replaced. The picker stores an asset:// reference that survives changes.

Next

• Use assets in your design: Themes & styling.
• Embed images in templates: Blocks reference.