How is the whole approval process configured on the system?

The entire approval process is designed and configured on the system: an admin defines the processes (what requires approval, by action key), builds each one's approver chain (steps with roles or specific users), and manages requests (viewing pending ones, seeing the decision chain). So governance is self-service configuration, not hard-coded policy — the organization models its own…

The entire approval process is designed and configured on the system: an admin defines the processes (what requires approval, by action key), builds each one's approver chain (steps with roles or specific users), and manages requests (viewing pending ones, seeing the decision chain). So governance is self-service configuration, not hard-coded policy — the organization models its own approval rules and hierarchy, and the engine enforces them. Pending requests, their chains, and their outcomes are all visible and auditable.