Automation
Automation keeps recurring compliance work running without manual coordination. We give you a small set of tools, each suited to a different shape of work:
- Workflows Coming Soon: gate object changes behind reviews. Define triggers and conditions, and the engine stages changes, routes approvals, and tracks the decision trail.
- Workflow Definitions Coming Soon: the authoring reference for writing definitions, covering triggers, Common Expression Language (CEL) expressions, actions, and copyable examples.
- Campaigns: collect something from many people at once, such as policy attestations, training acknowledgements, and vendor questionnaires. Recipient-level tracking and follow-up resends are built in.
- Assessments: the reusable questionnaire content campaigns send. Maintain one definition; run it as many times as you need.
- Tasks: individual owned work with a deadline.
None of these depends on the others to be useful; you can run campaigns without ever defining a workflow, or use tasks alone. They compose where it helps: a campaign distributes an assessment and tracks every recipient's response; an approval workflow assigns its reviews as work items.
Picking the Right Tool
| You need... | Reach for |
|---|---|
| Policy changes reviewed and approved before they take effect | A workflow with pre-commit approval |
| Every employee to attest to the acceptable use policy annually | A campaign targeting personnel |
| 40 vendors to complete a security questionnaire | A campaign sending an assessment |
| One person to upload specific evidence by Friday | A task |
Recurring governance work (access reviews, attestations, evidence refresh) is the easiest part of a program to fall behind on. Running it through automation standardizes the cadence, reduces manual handoffs and missed deadlines, and leaves a traceable record for audits and customer assurance: who was asked, who responded, who approved, and when.