# Manage suppressions

A suppression prevents transactional email from being sent to an address that should no longer receive it.

## Why suppressions matter

Repeatedly sending to invalid recipients or people who reported a message as spam damages sender reputation. Prontuno keeps a team-level suppression list so every application using that team can respect the same recipient state.

## Suppression types

- Type | How it is created | Can you remove it?
- Manual | A team member adds the address in the dashboard. | Yes, if your role has permission.
- Hard bounce | Prontuno records a permanent delivery failure. | Contact support.
- Spam complaint | The recipient reports a message as spam. | Contact support.

Automatic suppressions protect your sender reputation and cannot be removed from the dashboard.

## Add a manual suppression

1. Switch to the team that sends the email.
2. Open **Suppressions**.
3. Select the option to add a suppression.
4. Enter the recipient’s email address.
5. Confirm the addition.

Use manual suppressions for account closures, legal or support requests, known role accounts that should not receive a workflow, and any recipient your application must stop contacting immediately.

## Remove a manual suppression

Remove a manual suppression only after confirming that the address is correct and the recipient should receive transactional email again. Locate the address in **Suppressions** and delete it.

If the suppression came from a hard bounce or spam complaint, contact [support@prontuno.com](mailto:support@prontuno.com). Include the address and the reason you believe the suppression should be reviewed. Do not repeatedly recreate or resend the same message while waiting.

## Keep your application in sync

- Subscribe to `email.bounced` webhooks and mark permanent failures in your own database.
- Use the event ID to process each webhook once.
- Stop triggering messages for permanently invalid addresses.
- Fix address typos before asking for a suppression review.
- Keep product-level notification preferences separate from delivery suppressions.

## Suppression versus notification preference

A suppression is a delivery safety control. A notification preference decides which optional product notices a user wants. Your application should still manage its own preferences and avoid submitting messages that a user has disabled.

## Next steps

Learn how bounce events appear in [email statuses and logs](https://prontuno.com/docs/deliverability/understand-email-statuses-and-logs/).