Signal rules: which signals fire, per profile

Settings → Account rules → Signal rules (admins) has two tabs. It opens on Set your own rules; Default rules beside it explains, in plain words, what raises each built-in signal and at what severity. Set your own rules is one matrix: a row for every signal type, grouped, and a column for every profile, built-in and custom.

Each cell says whether that profile gets that signal, and from what severity:

• On / off — a switch.
• Minimum severity — Any severity, Medium and high, or High only.
• Tune (on signals with a threshold) — change when it fires for that profile; leave a box empty to keep the default. You can tune: health drop's trend (points and days), how many readings in a row, and the clear-again margin; onboarding's per-stage limits and "no first value" days; champion loss's rhythm factor; expansion's seats/volume-used % and growth %; low usage's "judge pace after" days and Mixpanel relative drop %; how many days early Early credit exhaustion needs (default 1) and how far over Credits over allowance needs (default 0%). The credits pace bands themselves (Under-using / Ahead of pace) are set per profile in Health rules.

Copy one profile's column onto another, or Reset to defaults. Nothing changes until you press Save signal rules; "Unsaved changes" reminds you.

How the rules applyCopy Anchor Link

• They cover every automatic source: integration syncs, agents, workflows and CSV imports. A signal that is off, or below the minimum severity, is simply not created.
• Signals already open stay open when you turn a type off, and still close themselves when the condition clears.
• Workflow / custom covers any signal type a workflow names that isn't listed.
• Signals a person creates, or asks Larry to create, are always allowed.