> ## Documentation Index
> Fetch the complete documentation index at: https://docs.encoreos.io/llms.txt
> Use this file to discover all available pages before exploring further.

# Suppressions

> View and manage the communications suppression registry — filter by channel, reason, and source; remove suppressions with audit logging.

The Suppressions page at `/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

<Steps>
  <Step title="Open Suppressions">
    Navigate to `/ce/suppressions` from the CE compliance navigation.
  </Step>

  <Step title="Filter records">
    Use the **Channel**, **Reason**, and **Source** dropdowns to narrow the list. Changing any filter resets to page 1.
  </Step>

  <Step title="Review suppression details">
    Each row shows the contact name, email, suppressed channels, suppression reason, source, and the date last updated.
  </Step>

  <Step title="Remove a suppression (admin only)">
    Click the trash icon on a row (requires `ce.suppressions.delete`). Confirm the dialog — the action is logged in the compliance audit trail and the contact may receive communications on previously suppressed channels.
  </Step>
</Steps>

## 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

<Columns cols={2}>
  <Card title="Community Engagement" icon="bullhorn" href="/ce/overview">
    Community Engagement core overview.
  </Card>

  <Card title="Governance & parity" icon="scale-balanced" href="/governance/index" />
</Columns>

<Note>
  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.
</Note>

<Accordion title="Documentation sources">
  * src/routes/ce.tsx
  * src/cores/ce/pages/SuppressionsPage.tsx
  * src/cores/ce/hooks/useSuppressions.ts
  * src/platform/table-v2/DataTable.tsx
</Accordion>