Reference
Workflows and approvals
One approval engine sits behind every module. Here is how a workflow is built, bound to a tool and run.
What a workflow is The graph in plain terms: blocks, paths, and what a run looks like while it is happening. Templates and runs An organisation owns the shape, a project names the approvers, and every run is a copy. The workflow builder The canvas, the happy path, and the reject lane that loops back. Assigning approvers By person, by permission, or by a field on the record itself. Binding a workflow to a tool Defaults, inheritance, and locking an organisation default in place. Approving and rejecting The approver's side, from My Items, from an email, and with an attachment.