Every business that runs on a Filament admin panel eventually hits the same wall: something needs a human to say "yes" before it happens. A purchase order over a threshold. A refund. A new vendor. A price change. A content post going live. Out of the box, Filament has no concept of "this record is waiting for someone to approve it" — so teams bolt on a status column, a few if-statements, and an email, and quietly reinvent an approval system badly, one project at a time. Approval Flows for Filament is that missing piece, built once, properly, as a plugin you drop into any Filament panel.

Approval Flows adds configurable, multi-step human approval chains to Filament resources. You define who has to approve what and in which order; your users submit a record, watch it move through the chain, and act on the ones waiting for them from a dedicated inbox. It is pure PHP and Livewire — no separate service, no external workflow engine, no JavaScript build step — so it installs like any Composer package and lives entirely inside the panel you already have.

Approval Chains, Not Just an "Approved" Checkbox

The core of the plugin is a real chain engine. A flow is a sequence of steps, and each step resolves to one or more approvers. Steps can require any one approver to sign off, or all of them, before the record advances. Approvers aren't hardcoded — they're resolved at runtime, so a step can point at a specific user, or at a role (every "Finance Manager"), and the right people surface automatically. When the last step clears, the record is approved; if anyone rejects, it stops. Submitters can cancel a request they own and resubmit after changes, so a rejection is a conversation, not a dead end.

The Approval Inbox

Approvals die when they're invisible. Approval Flows ships a dedicated Inbox page inside Filament that shows each user exactly the requests waiting on them — resolved with a single efficient query, not by loading every pending record and filtering in PHP. A manager opens the panel and sees "3 waiting," finance sees "1 waiting," and the work moves. Every decision is recorded, so the record carries its own approval timeline: who submitted it, who approved or rejected each step, and when.

Delegation and Escalation, Because People Go on Holiday

Real approval processes break the moment an approver is unavailable. The plugin handles this directly: an approver can delegate their authority to a deputy, and flows can escalate automatically when a step sits too long — driven by a schedulable command (approval-flows:check-escalations) that you point your cron at. Notifications go out over both database and mail channels, so nothing waits silently in a queue nobody is watching.

Built to Survive Your Filament Upgrade

A plugin is only useful if it keeps working. Approval Flows is tested green on both Filament v4 and Filament v5, with a CI matrix running across PHP 8.3 and 8.4, so a panel upgrade doesn't strand you. It integrates cleanly with Spatie's permission package for role-based approvers — in fact one of the first hardening fixes was making role resolution work correctly for every Spatie-based install, backed by a regression test so it stays fixed. A HasApprovals trait turns any Eloquent model into an approvable record, and a ready-made submit action wires the whole flow into an existing resource with a few lines.

How It's Sold

Approval Flows for Filament is a one-time purchase, not a subscription: $59 for a single project, $199 for unlimited projects, each including a year of updates. It's distributed through Anystack — the same marketplace the Filament core team uses — which handles licensing and the private Composer repository, so installation is a normal composer require against your license key. Full documentation (defining flows, approver resolution, delegation and escalation, notifications, events and hooks, multi-tenancy) and a live demo panel where you can submit a purchase order and watch it move through a real chain both live at approval-flows.talivio.com.

Why We Built It

This is Talivio's first premium Filament plugin, and we chose it deliberately: the leading free approvals package was abandoned going into Filament v4, and the paid alternatives are general automation engines aimed at a different problem — not focused human approval chains. That left a clear gap for a well-made, upgrade-safe, single-purpose tool that does one job the way a team actually needs it. Approval Flows is that tool: the "someone has to approve this first" layer Filament never shipped, done once so you never have to build it again.