Loading…
Open-Policy Exchange
~6 min to deploy
Salesforce Regulated-Account Action Gate
Holds account changes on regulated or restricted customers until the right reviewer signs the record.
For: Compliance and service ops handling regulated customers in Salesforce
SOC 2 CC6.1ISO 27001 A.5.34Regulated action evidence
What it enforces
Restricted-customer block
Blocks any action on a customer flagged restricted.
Elevated-risk escalation
Escalates actions on accounts whose risk score is in the elevated band.
Human-approval requirement
Escalates whenever the record itself carries a requires-human-approval flag, no matter the score.
salesforce-regulated-account-action-gate.yaml
# Salesforce Regulated-Account Action Gate
# Fork: thresholds mirror the "Regulated customer actions" template.
apiVersion: decionis.dev/v1
kind: PolicyPack
metadata:
name: salesforce-regulated-account-action-gate
surface: salesforce
workflow_key: regulated_customer_action
standards: [SOC2-CC6.1, ISO27001-A.5.34]
defaults:
mode: shadow
emit_dossier: true
rules:
- name: restricted_customer_block
when: "action == 'account.update'"
decision: |
BLOCK IF restricted == true
ALLOW OTHERWISE
reason_code: restricted_customer
- name: elevated_risk_escalation
when: "action == 'account.update'"
decision: |
ALLOW IF risk_score < 60
ESCALATE IF risk_score < 85
BLOCK OTHERWISE
reason_code: risk_score_over_threshold
- name: human_approval_requirement
when: "action == 'account.update'"
decision: |
ESCALATE IF requires_human_approval == true
ALLOW OTHERWISE
reason_code: record_requires_human_approval
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
Follow the install path for this surface, then paste the forked YAML as your policy config.
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.