Alert types and severities
Every alert Together raises, what triggers it, and how serious it is.
Alerts are typed and severity-tagged. The type tells you what; the severity tells you how urgent. The two together drive how alerts are sorted in the queue.
Severities
| Severity | Meaning |
|---|---|
| INFO | Informational. Worth recording in the audit trail but not actionable. Common for SYNC_COMPLETE. |
| WARNING | Something needs your attention soon. Default for cap-band alerts (AMBER, RED) and disclosure DUE_SOON. |
| CRITICAL | Stop and act now. Cap exceeded, disclosure overdue, sync errors that may have lost data. |
Alert types
| Type | Severity | Trigger | What it tells you |
|---|---|---|---|
| CAP_AMBER | WARNING | Donor's annual aggregate crossed the amber band (default 60% of cap, configurable per org). | Trending toward the cap. Note it; no urgent action. |
| CAP_RED | WARNING | Donor's annual aggregate crossed the red band (default 90% of cap). | Close to the cap. Talk to the donor before accepting more. |
| CAP_CRITICAL | CRITICAL | Donor's annual aggregate crossed the critical band (default 98% of cap). | Imminent breach. Verify identity, aggregate, and decide whether to refuse further donations. |
| CAP_EXCEEDED | CRITICAL | Donor crossed the cap entirely. | Legal breach. Refund the excess; escalate to your compliance lead. |
| DISCLOSURE_TRIGGERED | WARNING | Donor crossed the period-aggregate disclosure threshold (default $5,000 for the post-2027 regime). | A return is now owed for this donor in the current period. |
| DISCLOSURE_DUE_SOON | WARNING | A disclosure return is due in the next 14 days. | Start preparing if you haven't already. |
| DISCLOSURE_OVERDUE | CRITICAL | A return that should have been filed is past its deadline. | File immediately; engage the AEC about late lodgement. |
| POTENTIAL_DUPLICATE | WARNING | Together's duplicate scanner identified two donor records as the same person. | Merging may push aggregates over thresholds. Resolve via the donor queue. |
| SYNC_ERROR | CRITICAL | A scheduled CRM sync failed (NationBuilder, Raisely). | Data may be missing or stale. Reconnect or talk to support. |
| SYNC_COMPLETE | INFO | A scheduled CRM sync finished cleanly. | Confirmation. Dismiss in bulk if you don't want them in the queue. |
How severity drives the queue
The alert queue at Compliance -> Alerts sorts by severity descending then timestamp descending. CRITICAL alerts surface first, then WARNING, then INFO. Within a severity, newest first.
The severity-filter pill at the top of the queue is the fast triage tool: filter to CRITICAL during the morning compliance check, then sweep WARNING during the week.
How thresholds are set
Cap band thresholds are configured at Settings -> Compliance:
- Amber threshold (default 60%). The first warning band.
- Red threshold (default 90%). The serious band.
- Critical threshold (default 98%). The "about to breach" band.
You can adjust these per org if your team prefers earlier or later warning. The defaults are tuned for daily review of the queue.
What to do next
- Walk the queue for the first time: Resolve a compliance alert.
- Set the thresholds if the defaults are wrong for your team: Turn on Compliance.