How do you define what requires approval (ActionKey)?

You define which actions require approval by configuring an approval process tied to an action key — the identifier for the kind of action being governed. So the business decides exactly what needs sign-off (and what doesn't), turning approval on for the actions that matter. Defining requirements by action key means the approval engine is general: any action the system exposes for…

You define which actions require approval by configuring an approval process tied to an action key — the identifier for the kind of action being governed. So the business decides exactly what needs sign-off (and what doesn't), turning approval on for the actions that matter. Defining requirements by action key means the approval engine is general: any action the system exposes for governance can be placed under an approval process without bespoke code.