Statuses and approvals
Define a per-project copy status workflow in KopiMark, assign text and image nodes to teammates, and use statuses to drive review, approvals, and shipping.
Open as Markdown Full docs bundle
Open this page in
Statuses are how KopiMark tracks “is this copy ready?”. They sit on every text and image node, and they’re how a writer hands work off to a reviewer, a reviewer hands off to a stakeholder, and so on.
Most teams under-use this feature because the default works fine — the first time you customise it, the editor becomes a real review tool rather than a glorified text box.
How statuses work
- Statuses are defined per project (Marketing and Product can use different flows).
- The first status is the default — every newly-edited node picks it up automatically, so you never have to remember to set it.
- The first status cannot be deleted, but it can be renamed and recoloured.
- Statuses appear as small coloured pills in the editor, the page grid, and the activity log.
A common pattern:
Draft → Needs review → Reviewed → Approved → ShippedYou can have as many as you want. Three to six tends to be the sweet spot.
Create or edit your statuses
-
Open a project and go to Project Settings → Statuses.
-
Click New status.
-
Give it a name and pick a colour from the swatch picker.
-
Click Add.
To edit an existing status, click its name to rename inline (Enter to confirm), or click the colour swatch to recolour. Use the up/down arrows on each row to reorder.
The first status is the default and can’t be deleted. Re-ordering changes which status is the default. If you want a different default, drag the new one to the top first.
Assign a status to a node
On the canvas:
-
Click a text or image node.
-
In the side panel, click the status pill under the node title.
-
Pick a status from the list. The change is instant.
To change many at once, use the Bulk actions panel and choose Set status. You can scope it to the page, to a selection, or to nodes filtered by language/current-status.
Assign a node to a teammate
Statuses can carry an assignee. This is the most under-used feature in KopiMark, and the one that turns the tool into a real handoff system.
-
Set a node’s status (e.g. Needs review).
-
In the same picker, click Assign… and choose a workspace member.
-
They receive a notification — bell + email by default — with a deep link straight to that node.
The status pill now shows their avatar. When they open the editor, the Edited list in the side panel can be filtered to Assigned to me, giving them a clean queue.
Assignment notifications honour each user’s email preferences. If someone has turned assignment emails off in their profile, they still see the bell badge — they just won’t get the email copy.
Filter the page grid by status
The project page grid (where you see all the pages in a project) has a status filter at the top. Use it to:
- Find every page with Approved nodes ready to ship.
- Spot pages still in Draft before a deadline.
- Audit your reviewer’s pending queue.
Statuses also flow into export filters — see Export copy to ship only Approved nodes to your codebase.
A workflow that works
Most KopiMark teams settle on something like this:
- Writer edits a text node. It auto-picks-up Draft.
- Writer flips it to Needs review, assigns to a reviewer.
- Reviewer gets a notification, opens the deep link, comments if needed or flips status to Approved.
- Localisation lead bulk-translates the Approved nodes, sets Drafted on the translations.
- Each language reviewer flips to Reviewed per language.
- Engineer exports everything in Reviewed status.
It’s not the only flow that works, but if you’re not sure where to start, copy this one.