Approval System

The approval system sits between AI generation and publishing. It's a deliberate checkpoint: Borker generates, you decide, Postiz publishes.

The approval flow

flowchart TD
    A[Content generated] --> B{Auto-approval on?}
    B -- Yes --> C[Status: approved]
    B -- No --> D[Status: pending_review]
    D --> E{Reviewer action}
    E -- Approve --> C
    E -- Reject --> F[Status: rejected]
    E -- Edit + Approve --> C
    C --> G[Run Process Approved]
    G --> H[Status: scheduled]
    H --> I[Postiz publishes]
    I --> J[Status: published]
    F --> K[Archived]

Manual review mode

In manual mode (default), every generated content item lands in the Approval Queue with pending_review status. Reviewers can:

• Approve: mark it ready to schedule
• Reject: archive it; it won't be scheduled
• Edit then approve: inline edit the text before approving

The Approval Queue is the primary interface for content review. You can filter by status, platform, and date. See Approvals for the full UI walkthrough.

Auto-approval mode

In auto-approval mode, generated content skips human review and immediately moves to approved status. This enables a fully automated pipeline:

1. Daily workflow generates content
2. Content auto-approves
3. Process Approved runs and schedules everything
4. Postiz publishes on time

Enable this in Settings → Automation. You can still review auto-approved content before it's scheduled by checking the Approval Queue and rejecting items you don't want.

Approve ≠ schedule

This distinction matters. Approving content puts it in a "ready to schedule" state. It does not immediately send it to Postiz. Scheduling happens when you run the Process Approved workflow, which picks up all approved items and assigns them posting times.

This two-step design lets you:

• Review all content for the week before committing to any posting times
• Approve content in advance and schedule it later
• Run batch approval sessions separate from scheduling

Who can approve

Viewers can see the approval queue but cannot take action. Editors and above can approve, reject, and edit content.

See Roles for the full permissions breakdown.

What happens to rejected content

Rejected content is archived. It stays in the database with rejected status and won't be scheduled. You can view rejected items by filtering the Approval Queue to "Rejected."

Borker does not automatically regenerate rejected content. If you want a replacement post for a slot, you can:

1. Trigger the daily workflow again (it will generate new content for open slots)
2. Manually create a content item in the calendar

There's no feedback loop from rejection to the AI: rejecting a post doesn't directly teach Borker to avoid that type of content. If you're consistently rejecting content, that's a signal to update your brand voice config or topic angles. See Content Sounds Wrong.