The Suppressions page atDocumentation Index
Fetch the complete documentation index at: https://docs.encoreos.io/llms.txt
Use this file to discover all available pages before exploring further.
/ce/suppressions is a paginated registry of contacts suppressed from email, SMS, and/or phone outreach, with filtering and deletion capability.
Overview
Navigating to/ce/suppressions loads SuppressionsPage, gated by ce.suppressions.view. The page uses ListPageLayout with three filter dropdowns (Channel, Reason, Source) and a server-side paginated DataTable. Columns include contact name, email, suppressed channels (badges), reason, source, and last-updated date. Users with ce.suppressions.delete see a trash icon per row; clicking it opens an AlertDialog confirming that removing the suppression is logged in the compliance audit trail.
Who it’s for
Permission required:ce.suppressions.view (to view). Deletion requires ce.suppressions.delete.
Before you start
- Suppressions are created automatically by inbound opt-out keywords, bounce handlers, and the compliance dashboard — this page is for review and management.
- Removing a suppression is irreversible from this UI; the action is logged.
Steps
Filter records
Use the Channel, Reason, and Source dropdowns to narrow the list. Changing any filter resets to page 1.
Review suppression details
Each row shows the contact name, email, suppressed channels, suppression reason, source, and the date last updated.
Key concepts
- Channels —
email,sms,phone, or “All channels” (suppress_all flag). - Suppression reasons —
user_request,bounce,complaint,dnc_registry,legal_hold,opt_out_keyword,admin_override,other. - Suppression sources —
manual,sms_keyword,email_unsubscribe,dnc_import,bounce_handler,api. - Pagination — Page size options: 10, 25, 50, 100 records. Server-side pagination ensures performance at scale.
Related
Community Engagement
Community Engagement core overview.
Governance & parity
This page documents shipped product behavior. It is not medical, legal, or
billing advice. Verify against your organization’s policies and applicable
regulations before using it for clinical, compliance, or billing decisions.
Protected health information (PHI) shown in the product is governed by your
tenant’s access controls and is never exposed in this documentation.
Documentation sources
Documentation sources
- src/routes/ce.tsx
- src/cores/ce/pages/SuppressionsPage.tsx
- src/cores/ce/hooks/useSuppressions.ts
- src/platform/table-v2/DataTable.tsx