Approval Workflow

Review and approve content before it goes live. The approval system acts as a content lock — once approved, a post cannot be edited until unlocked.

How Approval Works

In FireBreath, approval is a content lock, not a publishing gate. This is an important distinction:

  • Scheduled posts will publish at their scheduled time regardless of approval status.
  • Approving a post freezes its content so nobody can change it before it goes live.
  • If nobody approves a post, it still publishes as-is at the scheduled time.

This design prevents missed schedules from forgotten approvals while still allowing content review.

Post States and Approval

  • Scheduled — The post is scheduled and its content is editable. It will publish at the scheduled time.
  • Queued (Approved) — The post is approved and locked. Content cannot be edited. It will publish at the scheduled time.

Approving a post moves it from "Scheduled" to "Queued". Revoking approval moves it back to "Scheduled".

The Review Queue

The Review page shows all posts that are ready for review:

  • Review Queue — Posts created via API or MCP that need human review.
  • Manual Queue — Posts flagged for manual posting on platforms that do not support API publishing.

For each post, reviewers can: - Read the content and see the target platform/account - Edit the text or schedule - Approve to lock the content - Reject or delete if needed

Unlocking a Post

If a reviewer approved a post but then realizes it needs changes:

  1. 1.Open the post in the Review Queue.
  2. 2.Click "Unlock to Edit".
  3. 3.The post moves back to "Scheduled" and content becomes editable.
  4. 4.Make the changes.
  5. 5.Click "Approve" again to re-lock.

This can also be done programmatically via the MCP server using the firebreath_approve_post tool with action: "revoke".

Tips

Design your workflow around your team: producers create content, reviewers lock it.
Approval is designed for non-technical approvers. The Review page is a simple web interface with Edit and Approve buttons.
If you want all posts to require approval before publishing, make it a team policy rather than a system gate. This keeps the schedule reliable.

Related

Was this page helpful?