Approval workflows you can actually configure

The building blocks: stages and roles

A Useboards approval flow is a sequence of stages, and each stage lists the roles allowed to approve it. Two rules govern how a request moves through them, and together they cover most real approval patterns:

• ANY-of within a stage: the first holder of any listed role to approve closes that stage — so “any of the three system owners can sign off” works out of the box.
• ALL-of across stages: every stage must clear in order before the grant is provisioned — so “owner approves, then security signs off” is a two-stage chain.
• Notification-only stages: inform a stakeholder (say, the finance owner) as the request passes, without making them a blocker.
• Multiple approvers per stage by role or by explicit email, so coverage doesn’t depend on one person being online.

Per system, per access level

The same product rarely deserves the same chain at every tier. In Useboards, each system defines its own approval flow, and you can override that flow for a specific access level. Read access might auto-approve or take a single owner sign-off; the admin tier on the same system can require a stricter multi-stage chain. That per-(system, access level) override is what keeps the workflow proportionate — you’re not forced to make everyone jump through the strictest hoop, or to loosen the strictest one to keep things moving.

When approval isn’t the right tool

A good workflow engine also knows when to get out of the way. Useboards routes some access outside the approval flow on purpose, because forcing it through one would be worse. Revokes execute immediately — delaying the removal of access is a security and compliance risk, so the authorization to revoke is the trigger, not another queue. Group-derived access is provisioned when someone joins the group, because membership is the unit of authorization; you approve the join, not each downstream grant. And when a system has no flow at all, low-risk requests auto-approve rather than manufacturing busywork.

• Revokes skip the queue and execute immediately.
• Privileged-group membership is approved at the join, not per entitlement.
• Systems with no flow defined auto-approve low-risk access.

Everything is recorded

A workflow is only as good as its trail. Every approval, decline, and notification in Useboards is captured — who acted, when, and on which stage — in an append-only audit log. Approvers see what’s waiting on them in a single queue, and the whole chain for any past request stays reconstructable when an auditor asks how access was authorized. The workflow you configured is the same one your evidence reflects.