Resolve a compliance alert
An alert means Together found something worth your attention. Walk the queue, mark each one once you've addressed it, and keep the dashboard honest.
Alerts fire automatically when a donor crosses a cap threshold, triggers a disclosure obligation, or sync errors on an upstream source. They're not blocking; donations continue to flow. But unresolved alerts pile up and obscure new ones.
Before you start
You need:
- ADMIN or EDITOR role on your org.
- Compliance module active. See Turn on Compliance if not.
Read the queue
Go to Compliance -> Alerts. The queue lists every alert your org has generated, newest first.
Filter the list using the pills:
- Type. Cap alerts, disclosure alerts, duplicate matches, sync errors.
- Severity. INFO, WARNING, CRITICAL.
- Read state. Unread / read.
The tab bar at the top separates Alerts (cap and disclosure issues) from Sync (upstream connector status). Both are alerts under the hood; the separation is for triage convenience.
Resolve an alert
Click any alert card to see the detail. Each card shows the donor (if applicable), the trigger, the timestamp, and the action you can take.
Two actions are available from the queue:
- Mark as read. The alert stays in the queue but moves out of "Unread". Use this once you've reviewed and there's no further action needed.
- Dismiss. The alert is removed from the active queue. Use this for noise (e.g., a duplicate alert you've already dealt with on the donor side, or a sync error that's already been retried successfully).
Both actions support multi-select. Tick the boxes on multiple cards and use the bulk-action bar at the top of the list.
Together also auto-dismisses a donor's open disclosure alerts when a refund, a manual void, or a CRM-sync cancellation brings that donor back below the disclosure threshold for the year - the obligation that raised them no longer needs filing, so there is nothing left to action.
What each alert means
| Alert type | What triggered it | Typical action |
|---|---|---|
| CAP_AMBER | Donor's annual giving crossed your amber threshold (default 60% of cap). | Note the donor; consider how their pattern is trending. Mark as read. |
| CAP_RED | Donor's annual giving crossed your red threshold (default 90% of cap). | Talk to the donor before the next gift. Decide whether to refuse further donations or accept them with eyes open. |
| CAP_CRITICAL | Donor's annual giving crossed your critical threshold (default 98% of cap). | Stop. The next donation is likely over the cap. Verify the donor's identity and aggregate before accepting anything else. |
| CAP_EXCEEDED | Donor crossed the cap. By law, you should not accept further donations from this person in the current period. | Refund the excess, log the breach internally. Talk to your compliance lead immediately. |
| DISCLOSURE_TRIGGERED | Donor crossed a disclosure threshold that creates an obligation. Victoria: $1,290 for the 2026-27 financial year, live now. Federally this alert commences 1 Jan 2027 at $5,000 per calendar year — the pre-2027 federal threshold of $17,300 is informational, so a crossing shows on the donor's compliance tab but raises no obligation, alert or deadline (the FY 2026-27 stub return is due 11 Mar 2027; diarise that yourself). | File a return. See File a disclosure return. |
| DISCLOSURE_DUE_SOON | A disclosure return is due in the next 14 days. | Get the return ready. Federal deadlines from 1 Jan 2027 fall on the 21st of the following month; election-period deadlines are 7 days per donation; expedited 24 hours. Victorian returns are due 21 days from each gift, with no election acceleration. |
| DISCLOSURE_OVERDUE | A return that should have been filed by now hasn't been. | File immediately; talk to the AEC about late lodgement. |
| POTENTIAL_DUPLICATE | Together's duplicate scanner flagged two donor records as the same person. | Resolve via Donors -> Duplicates. Merging may push aggregates over thresholds; check the dashboard after. |
| SYNC_ERROR | A CRM sync (NationBuilder, Raisely) failed. | Read the error detail. If it's a re-auth issue, reconnect at Settings -> Integrations. If unclear, talk to Together support. |
| SYNC_COMPLETE | A scheduled CRM sync finished successfully. Informational only. | No action. Dismiss in bulk if you don't want them in the queue. |
What to do next
- File a disclosure if you saw DISCLOSURE_TRIGGERED: File a disclosure return.
- Check the donor's compliance detail by opening Compliance > Donors and clicking the donor row - it shows their cap position and every obligation, per jurisdiction.
- Request an election period if a federal election is on: Request an election period.
- Read the regime for context on why each threshold matters: The federal regime.