The Asset Library is your central hub for every visual and brand asset generated across Eklipsa. It keeps approved logos, illustrations, imagery, and patterns organized so you can find, reuse, and manage them without digging through individual tools. For owner/admin roles, it is also where assets are published to client workspaces for portal review.
Click Halo Assets in the sidebar (also called Asset Library). You can also jump to it from any tool's saved-assets section via the "View in Asset Library" link.
What's in the Asset Library
Every asset you save from Halo Studio tools — logos, icons, color palettes, typography specimens, illustrations, patterns, and imagery — appears here automatically, tagged with the tool that created it.
Visual assets now show thumbnail previews on cards so you can identify the right file quickly without relying on file names alone.
Logos, icons, illustrations, patterns, and photos generated from Visual Foundation workshops and Halo Studio tools.
Assets are auto-tagged by source tool, workshop step, and type. Add custom tags to create your own organizational system.
Star your best assets for instant access. Favorited items appear in a dedicated quick-filter view.
Filter by asset type, source tool, date, or tag. Use keyword search to locate assets across your entire library.
Owners/admins can select Studio saves and strategy deliverables in the library (checkbox on each card), then publish to eligible client workspaces so reviewers only see approved deliverables in /portal. The first publish stores version 1 for that workspace if the item has no portal history yet. Publishing shares the same library item — it does not create a second card. After a client asks for changes, use Create Revision on the Client Portal Reviews tab (not a new library card). Pictures (logos, icons, illustrations) appear as images, including generated visuals that have a file but no document text. Text documents appear as formatted pages (with a Word download, including on no-login review links). If a Gamma deck exists for that item, reviewers open the presentation instead of the markdown outline, and can download the Gamma export file when one is available. Color palettes appear as selectable color chips.
Published assets with reviewer feedback feed the Client Portal Reviews tab. Open Review feedback to read and reply to live-view comments in the app.
How to Organize Your Assets
Star the assets you use most or that best represent your brand. This makes them easy to find when building campaigns or exporting guidelines.
Update each asset's title and description directly in the library card/list view so non-visual content is easier to search and retrieve later.
Create tags like "Q2 Campaign," "Social," or "Client Approved" to group assets by project or purpose beyond the automatic labels.
Remove outdated or rejected variants to keep the library focused on approved options.
Use the Publish to client portal icon on an asset card (or bulk Publish) to choose which client workspace can see that asset in /portal. This shares the same item with reviewers — it does not add a duplicate card in the library.
After reviewers comment or annotate published assets, finalize outcomes on the Client Portal Reviews tab, then reuse approved versions across tools for consistent brand execution.
Brand Intelligence: alignment scores on assets
Assets generated with strategy context show extra metadata on the card so you can see, at a glance, how on-brand each piece of output is.
A 0–100 score is shown on each tracked card. Hover for the tooltip: "Alignment score: X/100 — checked against brand rules". Green = 90+, amber = 70–89, red = below 70.
Small chips (e.g. Positioning, Tone of voice, Audience) show which strategy fields the tool referenced when it generated the asset.
Cards scoring below 70 get a red Fix this button. Click it to jump to Rewrite to brand with the asset's text pre-filled, then refine until the score is back in the green.
Use the Needs attention filter to see only at-risk (sub-70) tracked assets — the fastest way to triage what needs a rewrite.
Older assets that predate Brand Intelligence scoring still appear in the library — they just don't carry an alignment score or attribution chips.
Source filter
The Asset Library is a single view. Use the Source dropdown in the filter bar to narrow what you see:
- All sources: Studio saves plus strategy outputs that never had a separate library row (deliverables, rewrites, messaging matrix cells, and similar).
- Studio saves: Logos, imagery, and other assets saved from Halo Studio and workshops.
- Strategy outputs: Everything tracked in Brand Intelligence (
generated_assets). - Strategy deliverables: Create deliverables such as Client Presentation, Positioning Report, and Messaging Framework — shown with readable titles, section counts, and export, open-in-Create, and delete actions. Deleting a deliverable removes it and its strategy links but keeps alignment history. Publishing to the client portal shares that same library item with reviewers — it does not add a second card in Asset Library. Hidden portal copies stay available to clients if you later delete the original.
- Rewrite saves: Outputs saved from Use this version in Rewrite to brand.
Legacy deep links such as ?dataset=brand-graph still work and map to Strategy outputs.
Where Assets Come From
Assets enter the library from several sources:
- Visual Identity Workshop: Saved outputs from each of the 7 workshop steps (logo, icon, color, typography, illustration, pattern, imagery).
- Halo Studio Tools: Any image or visual you save from tools like Imagery & Illustrations, Campaign Builder, or Social Post Generator.
- Manual Uploads: Drag-and-drop your own files to include external assets alongside AI-generated ones.
- Brand Intelligence tools: Rewrite to brand, Brand Book, Playbook, Campaign Builder, and Activate messages outputs surface in the Brand Intelligence assets tab.
Review your Asset Library monthly. Archive assets you no longer use and re-favorite current top picks. Use Show by alignment to find at-risk content first, then click Fix this to send it through the rewrite pipeline. A curated, on-brand library means faster, more consistent output from every tool that references it.