Cross-Org Suppression Sharing
Share suppression lists between organizations
Cross-Org Suppression Sharing
If you manage multiple organizations within Mailnaptic, cross-org suppression sharing lets you synchronize suppression lists between them. This ensures that an address suppressed in one organization is also blocked in others, preventing accidental emails to contacts who have opted out or bounced elsewhere.
Why Share Suppressions?
Businesses that operate multiple brands, divisions, or regional entities often maintain separate Mailnaptic organizations for each. Without suppression sharing, a contact who files a spam complaint against one brand could still receive emails from another — creating legal risk and damaging sender reputation across all your sending domains.
- Compliance — Regulations like GDPR and CAN-SPAM apply to the business entity, not individual brands. Sharing suppressions helps you honor opt-out requests comprehensively.
- Reputation protection — Hard bounces and spam traps affect deliverability across your IP pool. Suppressing known bad addresses everywhere protects all your organizations.
- Operational efficiency — Manually maintaining separate suppression lists is error-prone and time-consuming.
Setting Up Suppression Sharing
To enable sharing, navigate to Organization Settings > Global Suppression > Sharing. Click Link Organization and select the organization you want to share suppressions with. Both organizations must approve the link — the target organization will receive a sharing request that an admin must accept.
Sharing Modes
Mailnaptic offers two sharing modes:
- Bidirectional — Suppressions flow both ways. Any address added to either organization's suppression list is automatically blocked in the other. This is the recommended mode for most setups.
- One-way — Suppressions flow from a source organization to a target. This is useful when a parent company wants to push suppressions to subsidiaries without inheriting their lists.
What Gets Shared
By default, all suppression types are shared: hard bounces, spam complaints, manual additions, and compliance requests. You can customize this in the sharing settings to exclude specific categories. For example, you might share only hard bounces and spam complaints while keeping manual suppressions organization-specific.
Managing Shared Suppressions
Shared suppressions appear in your global suppression list with a badge indicating the source organization. You cannot remove a shared suppression from the receiving side — it must be removed at the source. This prevents accidental unsuppression and maintains a clear chain of responsibility.
Disconnecting Organizations
To stop sharing, go to the sharing settings and click Unlink next to the connected organization. Previously shared suppressions will remain in place but will no longer sync. You can choose to keep or remove inherited suppressions when unlinking.