The Safety Net protects your deliverability at the moment of sending. Allegrow connects to your sales-engagement platform (Outreach or Salesloft), and when a prospect is added to a sequence, it checks the prospect's email address first — invalid and risky addresses are prevented from being emailed before they can bounce and damage your senders' reputation.
Two resources control where that protection applies, and both mirror switches your colleagues use in the Safety Net area of the app:
Safety Net Mailboxes
When Allegrow connects to Outreach or Salesloft, it syncs every sending mailbox present in that platform — whether or not that mailbox is also connected to Allegrow for reputation monitoring. That's why this list is usually much longer than your connected-mailboxes list, and why the two shouldn't be confused: this list answers "whose sends are protected?", not "what is Allegrow monitoring?".
Each synced mailbox has an activated flag: when on, sends from that mailbox go through Safety Net checking. Many teams deliberately protect only a subset — Update Safety Net Mailbox flips one mailbox, and activated=true on the list shows the protected set.
Safety Net Sequences
The same protection can be steered per sequence (Outreach) or cadence (Salesloft). Each entry pairs a sequence with the workspace user who owns it, carries its own activated flag, and keeps the CRM's identifiers (crmSequenceId + service) so you can cross-reference it in your platform.
Toggling a sequence with Update Safety Net Sequence applies workspace-wide — one call switches that sequence for every owner it appears under, exactly like the in-app toggle. A typical use is switching the Safety Net off for an internal or test sequence where validation would be noise, and back on for anything customer-facing.
Note that if a sequence is deleted and re-created in your platform, it re-syncs as a new sequence with protection on — the safe default.