AdminDefine rules for when the system should notify your team — Slack, email, or webhook — based on reason codes and thresholds.When: When setting up alerting for a new guardrail or reason code.
Details
What this page is forDefine rules for when the system should notify your team — Slack, email, or webhook — based on reason codes and thresholds.
When to use itWhen setting up alerting for a new guardrail or reason code.
Powered byrisk.killswitch
Settings — Notification Rules
Configure where and when Polytraders sends alerts. Rules are evaluated per-envelope.
How notification rules work
Each rule matches on a trigger (envelope event + condition), then fires to a channel (Slack, email, webhook). Rules are evaluated in order. A matching rule fires and stops unless “continue” is set. All rules log to the Audit Log with reason codeGOV_NOTIF_RULE_FIRED.
Active notification rules
| Rule name | Trigger | Channel | Recipient | Status | |
|---|---|---|---|---|---|
| Killswitch tripped | RISK_KILLSWITCH_TRIPPED | Slack & email | #ops-alerts · ops@org | ||
| Exposure cap hit | RISK_EXPOSURE_CAP_HIT | Slack | #risk-alerts | ||
| Stale book detected | RISK_BOOK_STALE_15S | ops@org | |||
| Market halt detected | GOV_MARKET_HALT | Slack & webhook | #ops-alerts · webhook | ||
| Drawdown threshold breached | RISK_DRAWDOWN_BREACH | Email & webhook | ops@org · webhook |
Notification channels
Connect Slack, email, or webhook endpoints used by your rules above.
Slack
https://hooks.slack.com/services/***
connected
Email
ops@org-abcde.com
active
Webhook
https://ops.org-abcde.com/webhook/poly
active