Skip to content

Guide

Library and sharing

Everything the workspace has produced, in one list, and the tools for finding one thing in it again. The library is search-first, because after a few months you have more content than a list can usefully show.

One list, two ways to see it

All content is one list. You can show it as rows or as cards — the toggle above the list — and either way it is the same pieces, the same filters and the same actions. Rows fit more on screen; cards give each piece room for a longer excerpt.

Every piece shows the same facts: its title, its type (a blog, a LinkedIn post, a press release), where it is at, its Human score, who owns it, the brand voice it was written in and when it last changed. A private piece carries a small lock next to its title. A piece that was converted from another leads with its type and says what it was made from; the original says how many versions were made from it.

Every row and card carries the same actions. Open and Convert to another content type (where it is switched on) appear when you point at the piece, and the three-dot menu holds Move to folder, Duplicate, Runs (that piece's runs, on the Runs page), Move to Archive and — once the piece is at the Publish stage, or has gone out and been edited since — Mark as published, which adds a line to the piece's record of where it went and gives it the green Published mark. A piece already marked since its last save has nothing left to mark.

Where a piece is at

Each piece carries one word for where it is in the editor's four stages — Review, Humanise, Approve or Publish. It is the same word the editor shows when you open the piece, so the list and the editor never disagree. A green Published mark sits beside it once the piece has gone out somewhere; a published piece you rework shows both.

Review is remembered per browser

Confirming that a piece reads right is something a person does, not something the piece records, so it is remembered in the browser you did it in. On another machine the same piece shows Review again until someone confirms it there. That is also why the Stage filter uses the four checkpoints the piece itself records — Not humanised, Humanised, Approved and Published — rather than Review.

Filtering

One row of filters sits above the list. Each one opens a short menu, and every option shows how many pieces it would leave — so you can see that a term appears in eleven blogs and two emails before deciding which way to narrow. Whatever you apply appears as a chip beneath the row; remove one with its cross, or all of them with Clear all.

FilterWhat it narrows to
TypeOne kind of piece — blog, email, LinkedIn post, press release and so on.
StageHow far a piece has got — Not humanised, Humanised, Approved or Published — by the furthest checkpoint it has passed.
VoicePieces written in a particular brand voice — or, as its own option, pieces written with no brand voice at all.
ScoreA Human-score band — see below, and Human score for what it measures.
OwnerPieces created by one person.
UpdatedPieces changed in the last 7, 30 or 90 days.
FolderPieces filed in one folder, or filed nowhere.

The URL carries your view

Filters, search term and the rows-or-cards choice are all in the address bar. You can bookmark a view you use often, or send a colleague a link that opens exactly what you are looking at. A hand-edited or outdated link never breaks the page — values it does not recognise are simply ignored. Open a piece from a narrowed list and Library in the breadcrumb brings you back to the same list, filters and view intact.

Human-score bands

BandScore
High80 and above
Mid60 up to 80
LowBelow 60
Not scoredNo score exists for this piece

These are not the publish check's thresholds

The publish check passes at 75 and warns at 50. These bands cut at 80 and 60. They are different tools — one judges a single piece, the other groups a whole library — so a piece can pass its check and still sit in the mid band here. Neither number is wrong.

“Not scored” is a real category, not a failure. Pieces that never went through a scoring pass have no score, and treating that as zero would make a workspace look worse than it is. A score always reads the same way in the library: the number, coloured green from 80, amber from 60 and red below, or the words “Not scored”.

Organising

Folders

Folders group pieces by whatever matters to you — campaign, client, quarter. A piece lives in one folder, and folders are shared across the workspace rather than personal.

Search across everything first, folders second. Folders are for the things you return to as a set; search is for finding one thing.

Archive

Archiving takes a piece out of the library without deleting it. Archived pieces keep their content, scores and history, and can be restored. The Archive page lists each one with its type, when it was archived and when it will be deleted; Restore brings it back, and Delete forever — the only place it exists — asks you to confirm first.

This is the right home for superseded work — last year's version of a policy page, a campaign that ended. It keeps the record without cluttering the list.

Archived is not deleted, and deleted is permanent

Archiving is reversible. Deleting is not — a deleted piece and its scores are gone, and support cannot bring one back. Archive unless you are certain.

Private and shared pieces

A piece is private — only its owner can open it — or shared, meaning anyone in the workspace can. Private is the sensible default for a draft; sharing is what makes a piece a team asset.

This is entirely separate from a share link, below. A private piece can carry a public share link, and a shared piece can have none.

Working in bulk

Several pieces can be selected and acted on together, as rows or as cards. Tick the box on a row, or the corner of a card, or use Select all loaded above the list; a bar appears with Move to folder, Move to Archive, Mark as published and Export. Changing a filter or the search term clears the selection; switching between rows and cards keeps it.

Export downloads each selected piece as its own Markdown, Word or HTML file — the same files the editor's Export menu makes — one after another, with no zip; your browser may ask you to allow several downloads. Word files from here carry the text and byline but not the piece's image.

The selection honours the same permission rules as acting on each piece individually — a viewer selecting ten pieces still cannot change any of them, and the bar says so rather than failing silently. Export still works for a viewer; it reads, it changes nothing.

When something is missing

  • Check the workspace. Content never crosses between workspaces. The most common cause of a missing piece is looking in the wrong one.
  • Check the archive. Archived pieces do not appear in the main list.
  • Check the filters. A date window from a previous search will hide everything older than it.
  • Check it was ever created. A failed run makes no piece, and a voice sample never does. Both are visible in Runs.
  • Check whose it is. Another person's private piece is invisible to you by design.