When a termination event lands, prove access and payroll were actually revoked — not just ticketed.
For: HR ops and IT security closing the offboarding loop
Restrains closure of the offboarding until every entitlement is confirmed revoked.
Blocks the next payroll cycle from paying a terminated worker.
Escalates when the leaver held a privileged role that has no revocation record.
# Workday Offboarding Access Guard
# Fork: this is the hr pack's Offboarding Guard, expressed against the
# termination event.
apiVersion: decionis.dev/v1
kind: PolicyPack
metadata:
name: workday-offboarding-access-guard
surface: workday
workflow_key: offboarding_completion
standards: [SOC2-CC6.2, ISO27001-A.6.5]
defaults:
mode: shadow
emit_dossier: true
rules:
- name: access_revocation_confirmation
when: "event == 'worker.terminated'"
decision: |
RESTRAIN IF entitlements.revoked_count < entitlements.total_count
ALLOW OTHERWISE
reason_code: entitlements_still_active
- name: payroll_stop_confirmation
when: "action == 'payroll.pay_worker'"
decision: |
BLOCK IF worker.status == 'terminated'
ALLOW OTHERWISE
reason_code: payment_to_terminated_worker
- name: privileged_role_sweep
when: "event == 'worker.terminated'"
decision: |
ESCALATE IF worker.held_privileged_roles == true AND revocation_evidence == null
ALLOW OTHERWISE
reason_code: privileged_revocation_unproven
Fork it, change the thresholds to match your environment, and deploy in shadow mode first — it defaults to listen-only so nothing in your live pipeline changes.
Follow the install path for this surface, then paste the forked YAML as your policy config.
This recipe is one step in a path. The same five steps apply to every recipe in the exchange.
Run the policy against a realistic action in the browser. Push it past what the rules allow and watch the verdict come back. No account.
See exactly what was decided and why: the rule that fired, the evidence it read, the policy version in force, and an Ed25519 signature you can verify yourself.
Measure what the policy would have caught on your own traffic without touching the live path. Every recipe defaults to shadow, so the first deployment carries no execution risk.
Point the same policy at the system where the action actually originates — a checkout, an ERP posting, a Zap, an agent's tool call.
Publish the proof: a public verification link, an embeddable badge, a PR comment, or an anonymized shadow-mode finding. This is how the next person discovers Decionis.