Workflows for About + Policies

About sections and policies have a dedicated set of triggers and actions for the "publish → require acknowledgement → chase unread → review stale revisions" loop.

Useful triggers

• about.section_created / about.section_updated — fire when content changes.

• about.section_read / about.section_read_completed — fire when staff acknowledge.

• about.section_unread_for_days — fire on individual users who haven't read after N days.

• about.revision_stale_for_days — fire when the latest revision is older than N days.

• All five mirrored for policy.*.

Useful actions

• about.mark_required_reading / policy.require_acknowledgement — flag a section as required reading. Currently the ONLY way to set the ensure_read flag in the database — there is no UI control for it.

• about.remind_unread / policy.remind_unread — send reminder to staff who haven't marked it read.

• about.publish_section / policy.publish_section — publish a new section.

Common pattern: stale-review chase

1. Trigger: policy.revision_stale_for_days threshold 365.

2. Action: notify.email to the realm admin — "Policy [X] is due for annual review."

Common pattern: unread-reminder loop

1. Trigger: policy.section_unread_for_days threshold 7 with require_ensure_read = true.

2. Action: policy.remind_unread (or notify.email if you want a richer email).

Heads up — The about.section_unread_for_days and policy.section_unread_for_days triggers respect the require_ensure_read flag by default. Until a section is flagged as required reading (via about.mark_required_reading or policy.require_acknowledgement), those triggers fire for nothing.