Omniscio

Approval Workflows

Approval Workflows attach a multi-step sign-off chain to a board item: moving the item into a chosen status starts the chain, each step collects decisions from its own approvers under one of three rules, and the item records the outcome while the next approver is told in the inbox.

On this page

What it is

Approval Workflows is the sign-off engine for Mission Control boards. A workflow belongs to one board and names the column change that starts it — a status column plus the value that fires it. When an item moves into that value, the workflow opens a pending approval instance on the item, and the people named on its first step are asked for a decision.

A workflow is built from serial steps. Each step owns a list of approvers and one approval rule, so a chain can ask one reviewer, then a committee, then a final approver without any of them seeing the others' decisions first.

The feature ships hidden: the switch is in Settings → Lab (pmApprovalWorkflowsEnabled) and starts off, because the chain is still being finished.

Where to find it

  • A board's Approvals page lists the board's workflows and their trigger values, and the workflow builder creates, edits and deletes them.
  • Settings → Lab → Approval Workflows is the on/off switch for the whole surface.
  • The inbox carries a pending approval to each designated approver, with the item and the step it belongs to.
  • An item's History tab records the decisions as item history entries, so the audit trail lives with the item.

How it behaves

The three approval rules

Each step picks exactly one rule (approvalType):

Rule The step passes when
Any one (any_one) a single designated approver approves
All must approve (all_must_approve) every designated approver approves
Majority (majority) more approvers approve than reject

An approver can also answer changes requested, which ends the instance immediately with that outcome — the chain does not continue past a request for changes.

What starts a chain and what stops it

  • A chain starts only on an item_status_changed board event whose column and new value match the workflow's trigger. A workflow can only be triggered by its own configured pair, and only one active instance per item per workflow can exist, so a burst of status writes cannot open several chains.
  • Each decision is checked against the step's own approver list; someone who is not named on the current step is refused rather than silently ignored.
  • When a step passes, the instance advances to the next step and stays pending. When no step remains, the instance completes as approved. A failing decision completes it as rejected.

The instance statuses are pending, approved, rejected, changes_requested and cancelled; the last is reached through the explicit cancel path rather than through a decision.

In the board and the inbox

Every state change — a new instance, an advance, a completion — pushes an approval-changed event and is also published as a board event, so board automations can react to approval_changed the same way they react to a status change. Approvers are resolved by their stable user identity, and an approver's email is kept only as the fallback the inbox lookup uses.

Boards, items and roles are described in mission-control.md and mission-control-part-2.md. Every change an approval makes is recorded by pm-item-history.md. Every other page in this library is listed in INDEX.md.

Last verified 2026-11-10