---
title: "Review and approval, MailKaro Docs"
description: "Review and approval in MailKaro: move an email from draft to review, approval and published, with an audit trail."
---

# Review and approval

Collaboration & history

# Review and approval

Move an email from draft to review, approval and published, with an audit trail.

Every saved email can carry a status: `draft`, `in_review`, `approved` or `published`. The dashboard shows it in the email list and as a bar in the editor with the next step as a button. Without a status an email has never entered the workflow.

## The steps

- Anyone who can edit sends a draft for review. They can also withdraw it.
- An owner or an admin approves it, or sends it back to draft ("Request changes").
- On Enterprise, only an approved email can be published. Draft and in review go to approved first.
- Any editor can move a published or approved email back to draft.
- Changing the content of an email in review or approved sends it back to draft, so what was approved cannot change without another look. Renaming does not.

The review steps need the Enterprise plan (`governance.approvals`). On other plans an email only moves between draft and published. A view-only member sees the status but cannot change it. Every change is in the audit log with who made it, from which status to which.

## API

bash

```
curl -X POST https://api.mailkaro.com/{org}/designs/:id/status \
 -H "Authorization: Bearer <the signed-in user's session token>" \
 -H "content-type: application/json" \
 -d '{ "status": "in_review" }'
```

A refused move answers with an `error` and a readable `message`: `approver_required`, `approval_required`, `invalid_transition`, `approvals_not_available` or `no_change`.

ℹ Sending a design through `POST /v3/emails` is not blocked by its status yet. Check the status in your own flow if you need that.

Source: https://docs.mailkaro.com/review-approval