The agent gave you twelve good drafts. You used two.
Collections are named groups of generated posts and media you file as you go. A campaign, a batch of variants, a swipe file for next quarter. The other ten drafts stop being scrollback and start being a backlog you can actually reach.
Good work you cannot find is work you did not do.
You asked for ten variants, shipped two, and let the other eight scroll out of the conversation. Next month you ask for ten more and get roughly the same eight back.
The image you want is definitely in the library. So are nine hundred others. Filtering by date is not the same as remembering why you kept it.
The campaign is drafts, images, and a plan spread across three screens, held together by the fact that you happen to remember all of it right now.
Honest fit check
For you if
- You generate in batches and ship a fraction of what you generate.
- You plan campaigns as a set of posts and assets rather than one at a time.
- You keep a swipe file and would rather it lived where you post.
Not for you if
- You want nested folders, per-item permissions, and a full DAM taxonomy. This is a flat, fast shelf on purpose.
- You want an approval pipeline. Approvals are a workspace role gate, not something a collection does.
A shelf for the work between idea and calendar.
Not everything is ready to schedule, and not everything unready should be thrown away. Collections are the middle drawer that most tools skip.
Named groups, made in a second
Create a collection when you need one, name it what you will actually search for, and file into it as you work. No folder tree, no taxonomy meeting.
File from the agent
When the FoPost Agent produces a batch, keep the ones you are not shipping today instead of losing them to scrollback.
File from the media library
Group assets for a campaign, a client, or a season. The same asset can sit in more than one collection without being copied.
Deleting is safe
Removing a collection removes the grouping only. The posts and media inside it are untouched, which means you can reorganise without a moment of dread.
Workspace-scoped
A collection belongs to one workspace and is visible to the people in it. Nothing leaks between clients.
A short path back to the calendar
What is in a collection is a real draft or a real asset, not an export. Take one out and it goes to the composer and onto the calendar like anything else.
Four steps, none of them admin
Make a collection
One click, one name. Make it when the need appears rather than designing a structure in advance.
File as you work
Add drafts from an agent batch and assets from the media library. An item can live in several collections at once.
Come back to it
Open the collection next week or next quarter and the whole set is still together, in the workspace it belongs to.
Ship out of it
Pull a draft into the composer, attach an asset to a post, and schedule. Nothing has to be exported or recreated.
Publishes to all major networks