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 Queue
The Queue page keeps post review in one place:
- Drafts — Work-in-progress posts that are not ready to publish yet.
- Scheduled — API-connected posts that will auto-publish at their scheduled time and can optionally be locked first.
- Post Manually — Posts flagged for manual publishing on platforms or content types that do not support direct API publishing.
From Queue, reviewers can: - Read the content and see the target platform/account - Edit the text or schedule - Lock content before it goes live - Reject or delete if needed
Unlocking a Post
If a reviewer locked a post but then realizes it needs changes:
- 1.Open the post in the Queue page.
- 2.Click "Unlock to Edit".
- 3.The post moves back to "Scheduled" and content becomes editable.
- 4.Make the changes.
- 5.Click "Lock" again to re-freeze it.
This can also be done programmatically via the MCP server using the firebreath_approve_post tool with action: "revoke".