Loading…
Open-Policy Exchange
~3 min to deploy
Slack Discretionary-Spend Gate
Every spend approval ping above $5k carries the policy snapshot, the requester's authority, and a public verify URL.
For: Ops and finance teams releasing discretionary spend from Slack
SOC 2 CC8.1ISO 27001 A.5.15Spend approval evidence
What it enforces
Spend threshold
Escalates a discretionary spend release above $5,000 to the named approver.
Self-approval block
Blocks a release where requester and approver are the same person.
Budget-headroom check
Restrains a release that would take the cost centre past its remaining budget.
slack-discretionary-spend-gate.yaml
# Slack Discretionary-Spend Gate
# Fork: set the threshold and cost-centre budget source for your org.
apiVersion: decionis.dev/v1
kind: PolicyPack
metadata:
name: slack-discretionary-spend-gate
surface: slack
workflow_key: discretionary_spend_release
standards: [SOC2-CC8.1, ISO27001-A.5.15]
defaults:
mode: shadow
emit_dossier: true
rules:
- name: spend_threshold
when: "action == 'spend.release'"
decision: |
ALLOW IF amount_usd < 5000
ESCALATE OTHERWISE
reason_code: spend_over_approval_threshold
- name: self_approval_block
when: "action == 'spend.release'"
decision: |
BLOCK IF approver.email == requester.email
ALLOW OTHERWISE
reason_code: self_approval_not_permitted
- name: budget_headroom_check
when: "action == 'spend.release'"
decision: |
RESTRAIN IF amount_usd > cost_centre.remaining_budget_usd
ALLOW OTHERWISE
reason_code: exceeds_cost_centre_budget
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.
How to install it
Installs with no code. The Decionis app sits beside Slack approvals and records a Decision Dossier for every routed request.
Slack — shadow mode
1. Install Decionis from the Slack Marketplace.
2. /decionis → "Connect a workflow" → pick refund_approval (or any of the starter packs).
3. The app runs in observation mode out of the box: every Slack approval still
flows the same way, plus a signed Decision Dossier is recorded alongside it.Ships in shadow mode — every verdict is recorded, nothing is blocked.
What to do next
This recipe is one step in a path. The same five steps apply to every recipe in the exchange.
- Simulate this recipe
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.
- View the signed Decision Dossier
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.
- Deploy in shadow mode
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.
- Connect a real workflow
Point the same policy at the system where the action actually originates — a checkout, an ERP posting, a Zap, an agent's tool call.
- Share the verified result
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.