# 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. _Source: https://kopimark.com/docs/guides/statuses-and-approvals/_ 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 → Shipped ``` You can have as many as you want. Three to six tends to be the sweet spot. ## Create or edit your statuses 1. Open a project and go to **Project Settings → Statuses**. 2. Click **New status**. 3. Give it a name and pick a colour from the swatch picker. 4. 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. > _[image placeholder: Project Settings → Statuses with the colour swatch picker open on a status row.]_ ## Assign a status to a node On the canvas: 1. Click a text or image node. 2. In the side panel, click the **status pill** under the node title. 3. 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. 1. Set a node's status (e.g. *Needs review*). 2. In the same picker, click **Assign…** and choose a workspace member. 3. 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](/docs/guides/export-copy/) to ship only Approved nodes to your codebase. ## A workflow that works Most KopiMark teams settle on something like this: 1. **Writer** edits a text node. It auto-picks-up *Draft*. 2. Writer flips it to *Needs review*, assigns to a reviewer. 3. Reviewer gets a notification, opens the deep link, comments if needed or flips status to *Approved*. 4. Localisation lead bulk-translates the *Approved* nodes, sets *Drafted* on the translations. 5. Each language reviewer flips to *Reviewed* per language. 6. 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. ## See also - [Review with comments](/docs/guides/review-with-comments/) - [Translate with AI](/docs/guides/translate-with-ai/) - [Export copy](/docs/guides/export-copy/) --- ## All documentation _The full docs index, in case the answer lives on another page. Fetch any item as raw Markdown by appending `.md` to its URL, or grab everything at once from https://kopimark.com/llms-full.txt._ ### Start here - [Introduction](https://kopimark.com/docs/) - [Getting started](https://kopimark.com/docs/getting-started/) ### Concepts - [How KopiMark works](https://kopimark.com/docs/concepts/how-kopimark-works/) - [Figma sync and cache-only mode](https://kopimark.com/docs/concepts/figma-sync-and-cache/) - [Roles and workspaces](https://kopimark.com/docs/concepts/roles-and-workspaces/) ### Guides - [Connect Figma](https://kopimark.com/docs/guides/connect-figma/) - [If your Figma seat is limited](https://kopimark.com/docs/guides/figma-seat-and-rate-limits/) - [Invite your team](https://kopimark.com/docs/guides/invite-your-team/) - [Translate with AI](https://kopimark.com/docs/guides/translate-with-ai/) - [Review with comments](https://kopimark.com/docs/guides/review-with-comments/) - [Statuses and approvals](https://kopimark.com/docs/guides/statuses-and-approvals/) _(this page)_ - [Custom fonts](https://kopimark.com/docs/guides/custom-fonts/) - [Export copy](https://kopimark.com/docs/guides/export-copy/) - [API and developer tokens](https://kopimark.com/docs/guides/api-and-developer-tokens/) ### Settings - [A tour of Settings](https://kopimark.com/docs/settings/tour/) - [Profile settings](https://kopimark.com/docs/settings/profile-settings/) - [Workspace settings](https://kopimark.com/docs/settings/workspace-settings/) - [Project settings](https://kopimark.com/docs/settings/project-settings/) ### Reference - [Plans and limits](https://kopimark.com/docs/reference/plans-and-limits/) - [Keyboard and canvas](https://kopimark.com/docs/reference/keyboard-and-canvas/)