Workflow Access Control

Definition. The specification of who can view, modify, pause or deploy a workflow, and who can see its data, enforced by the platform rather than by convention. Access control is what prevents an unauthorised change from causing an outage or a data exposure.

How it works. Define roles: viewer, operator, developer and owner. Grant the minimum role needed. Require review for changes to production workflows. Separate the ability to deploy from the ability to approve, where the consequence is high. Log every access and change, and review grants quarterly.

Example. Any engineer can modify any workflow in production. A contractor changes a threshold in a payment workflow, causing 400 incorrect approvals before it is noticed. After implementing roles, only the workflow's owners can deploy to production, changes require review, and the contractor's role is read-only. The change control also records who approved each deployment.

Use case. Access control is required for any workflow with financial or personal data consequences, and it is a standard audit requirement. It is also a protection against accidental changes.

Warnings. Convention-based access control fails as soon as someone is in a hurry. Never let deployment and approval be the same person for high-consequence workflows. And never grant broad access because scoping is inconvenient.

Limitations. Role design requires understanding who needs what, and roles accumulate over time. Access control also adds friction to legitimate changes, which can encourage workarounds.

← Browse all glossary terms