Collections

A collection groups everything that belongs to one piece of work: the workflow that made it, the board it landed on, every creative, and any reference assets. Find the whole set, and hand it off, as one thing. Every factory launch files itself into a collection automatically, so nothing you produce is ever loose.

Examples

Collections scale from big to small:

• A campaign: the workflow that ran it, the board it landed on, every creative it produced, and a couple of reference PDFs.
• A subject: employee headshots across every department, plus the creatives from a staff-spotlight LinkedIn series. One collection whether it's 6 people or 6,000.
• A template shelf: a set of layouts for one recurring job, kept together so they're easy to grab.

Finding them

Collections in the brand nav is a three-pane, Finder-style browser: a tree on the left (collections → per-type groups → items), the open collection's contents in the middle (grid or list, remembered per collection), and a preview panel on the right with rename, status, and "open" actions.

A collection doesn't own what's in it: a creative still lives in the creative gallery, an asset still lives in the asset library. A collection just keeps a reference, so the same item can sit in more than one collection at once, and deleting a collection never deletes what was in it.

Adding items

• Automatically: a factory run files its output into a collection the moment it's produced (named from the run, or a collection you pick at launch).
• By hand: click Add items in any collection to add existing templates, assets, creatives, boards, or runs. Pick individually, search, or "add all matching" a tag.
• Move an item to re-home it in a different collection. One wrinkle: moving a board moves only the board, the creatives already on it keep their original collection, since a standing review board can outlive many campaigns.

Handing a collection to an agent

Because a collection is a project's whole working set, pointing an agent at one is often all the context it needs: "build the leadership page, the photos are in the Leadership collection" resolves in a single call. Agents read a collection's full manifest (every creative with its render URL, linked templates and assets with their metadata, credit spend) via get_collection (MCP), braaand collections get (CLI), or GET /api/brands/{id}/collections/{id}.

Working in the browser

• Multi-select works in both grid and list: check cards, then bulk-set status or remove from collection (never deletes the item itself).
• Selection mirrors to the URL, so any collection or item view is a shareable deep link.
• New pipelines can be launched from a collection's "…" menu, and the run files itself there from birth.