ForgeSendDocs

Compliance & suppression

Email compliance is already documented in full elsewhere; this page summarizes it and links out, then covers Suppression in full.

Email compliance

The Email compliance tab sets the workspace's default unsubscribe footer — a preset (Default, Reply-style, Minimal, Friendly) or a validated custom message, always requiring the {"{{unsubscribe_url}}"} placeholder.

Email compliance — read only

Unsubscribe footer

DefaultReply-styleMinimalFriendlyCustom

Full detail — every preset's exact wording, the 300-character cap, and validation rules — is covered in Workspace settings. A campaign can still override this with its own footer, covered in Campaigns overview.

Suppression

A single table of every suppressed email address in the workspace — nothing here is sent to, no matter which campaign or list it's on.

Suppression list — read only

Suppression list

Add email
EmailReasonDate addedRemove
marcus@webbindustries.comUNSUBSCRIBE7/12/2026Remove
bounced@oldcorp.ioBOUNCE7/9/2026Remove
competitor@rival.comMANUAL7/1/2026Remove

Reason shows exactly one of three raw values: UNSUBSCRIBE (an opt-out reply, or a footer link click), BOUNCE (a hard bounce), or MANUAL (added by hand from this tab). There's no search box and no pagination — the whole list loads at once. With nothing suppressed, it reads "No suppressed contacts — Emails you suppress will appear here."

Adding and removing entries

Add email reveals an inline form — just an email address, always saved with reason MANUAL.

Clicking Remove on any row un-suppresses that address immediately — there's no confirmation step. Removing a manually-suppressed competitor's address is reversible by nature; removing an address that bounced or unsubscribed puts it back into eligible sending with no extra warning.

Suppression is checked in several places, not just at send time: adding a suppressed address to a list is blocked outright, a CSV import skips suppressed rows, and enrolling leads into a campaign skips them too (both surfaced as counts in the add-leads preflight). It does not automatically pause leads already enrolled before the suppression was added — those are only skipped at actual send time, or cleaned up manually via the Remove from active send pool action in preflight.

Where to go next

Next: Developer & support