04. Approval workflow

Real approval flow. Not a checkbox bolted onto a scheduler.

In most teams, approving a post means a Slack DM, a screenshot, three follow-ups, and a manual paste into whatever tool actually publishes. Squawk's approval flow is built into the product: drafts move through real states, route to the right reviewers, and leave a clear audit trail.

A bluebird in a control tower waving in a paper-airplane post for takeoff
Screenshot todoApproval queue: clear states, clear ownershipapps/marketing/public/images/features/approval-workflow.png

What it does

The capabilities, one at a time.

Explicit states with audit trail

Needs review, approved, scheduled, published, rejected. Every state change is recorded with who did it and when.

Per-author and per-brand reviewers

Different posts can need different approvers. The CEO's posts route to the CEO. Client posts route to the client.

Inline comments and edit suggestions

Reviewers can leave comments, suggest edits, or push back to draft. The author sees the feedback in context.

Auto-approve for trusted authors

Configure which authors can publish without explicit approval (e.g. the founder posting from their own account).

Screenshot todoReview view: comments, edits, audit trailapps/marketing/public/images/features/approval-detail.png

Why it matters

The reason this exists.

For agencies serving clients, approval is the workflow. For small teams, approval is the thing that keeps marketing from being one person's part-time chaos. Either way, baking approval into the product (instead of bolting it onto a scheduler) is the difference between a workflow and a hope.