Automations & approvals

Work through the rule library

Rather than starting from a blank rule, the walkthrough opens the library and groups the options into families — escalation, notification, assignment, data changes. You browse what is available for this app, switch on what fits, and the active and inactive lists give you a running picture of what is live.

• Rule families — Escalate, notify, assign, or change a field.
• Templates — Common rules pre-built rather than written from scratch.
• Active / inactive — See at a glance which rules are switched on.

Triggers and actions

Each rule pairs an event with an action. The tour builds the useful ones explicitly: a corrective action sitting Open for seven days pushes its severity to High; a record untouched for forty-eight hours emails the owner. Note the difference — the first changes data, the rest only tell someone. Knowing which of your rules write is worth the two seconds it takes to check.

Hold the commit behind an approval

Any step that commits something — closing a finding, publishing a report, sending externally — can be routed to an approver first. The automation prepares the work and presents it; a person signs off. Speed on the preparation, judgement on the decision.

Why it matters

Full automation is fast and unaccountable; full manual routing is accountable and slow. Splitting them — machines do the moving, people do the deciding — gets you both, and it leaves an attributed trail showing exactly who approved what and when, which is the part an auditor asks about.