Use case

Campaign approval workflow software

Cohiva Campaign runs campaign approvals as configurable 1 to N stage chains over tasks, with internal users or external email-only guests as approvers. The state machine is enforced on the server, so a client cannot mark something approved by itself.

An approval workflow only protects you if it cannot be skipped. Cohiva Campaign models approvals as configurable stage chains over campaign tasks, from a single sign-off to as many stages as your review needs, and it enforces every transition at the API.

Each stage holds its own approvers. They can be internal users in your workspace or external email-only guests who review without a Campaign account, which suits the times you send work to outside counsel, a client, or a regulator-facing reviewer. A stage can require every approver to sign off, or advance as soon as any one of them approves, so you can model both consensus and first-available review.

When a reviewer rejects, the task routes back to in production with their comment attached, so the work re-enters the flow with the reason recorded rather than disappearing into an inbox. Nothing is lost, and the next person can see exactly what to change.

The point that matters most is enforcement. The approval state machine is server-enforced, which means a client cannot mark a task approved by itself. Advancement is computed on the server against the stage configuration, so the approval state you see is the approval state that actually happened.

That makes the workflow auditable as well as usable. Because every advancement and rejection is a server decision, your record of who approved what, and when, is a by-product of the workflow rather than a separate exercise. Start a free trial of Cohiva Campaign to put a non-bypassable go-live gate behind every launch.

Frequently asked questions

How many approval stages can I configure?
Campaign supports configurable 1 to N stage chains over campaign tasks, so you can model a single sign-off or a long multi-stage review.
Can external reviewers approve without an account?
Yes. A stage can include external email-only guests who review and approve without a Campaign account, alongside internal users.
Does a stage need every approver or just one?
You choose per stage. A stage can require all approvers to sign off, or advance on any one approval.
What happens when a reviewer rejects?
The task routes back to in production with the reviewer's comment, so the work re-enters the flow with the reason recorded.
Can someone mark a task approved from the client?
No. The approval state machine is server-enforced, so a client cannot mark a task approved by itself; advancement is computed on the server.

Related

Put a non-bypassable gate behind every launch

Cohiva Campaign rejects an unchecked go-live at the API and keeps an append-only audit. Try it free.

Start free trial