The Tuning Menu: Escalate, Silence, and the Advisor
3 min read
Four pages in Burrow sit together under Tuning in the left navigation because they are one toolkit for adjusting how loud Burrow is. Two of them pull in opposite directions, and the third proposes entries for both. This page is the map; each tool has its own detailed article linked below.
The three tools
Sensitive Sites / Sensitive Labels — Escalate ↑
Activity that touches a sensitive site path or carries a sensitivity label you have marked is treated as more severe — Burrow bumps the alert up a tier. Reach for these when Burrow is too quiet about something important: a Finance or Board site, a Confidential label whose movement should always get attention.
See Sensitive sites, labels, and keywords.
Exceptions — Silence ↓
Expected activity from a specific account (a user-plus-category pair) is auto-downgraded or suppressed. Reach for these when Burrow is too noisy about something benign: a service account doing its nightly batch, a vendor automation that always trips the same rule.
See Entity exceptions.
Suggestions — the advisor
Burrow watches your alerts and your team's dispositions and proposes entries for the other two tools. Apply on a suggestion writes the entry straight into Sensitive Sites or Exceptions — the Suggestions page holds no configuration of its own. (This is why an applied "add exception" suggestion also appears on the Exceptions page: same underlying store, one entry, shown in both places.)
See Tuning a noisy rule.
Rule of thumb
| If Burrow is… | Reach for… |
|---|---|
| too quiet about something important | Sensitive Sites / Labels (escalate ↑) |
| too noisy about something benign | Exceptions (silence ↓) |
| and you want it to propose either from what it already sees | Suggestions (the advisor) |
Where this fits with the deeper tuning model
The escalate / silence / advise triad is the orientation — which of the three Tuning pages to open. When you need finer control over a single rule's thresholds, the five-layer tuning model covers the rest: detection posture, per-rule overrides, the baseline-maturity gate, the persistence gate, and entity exceptions. Exceptions are the one lever that appears in both — the surgical, per-account layer.
See also
- Sensitive sites, labels, and keywords — the escalate ↑ tools.
- Entity exceptions — the silence ↓ tool.
- Tuning a noisy rule — the Suggestions advisor.
- The five-layer tuning model — the deeper per-rule controls.
Need help? support@smikar.com.