# Managing notifications

Creditor partners can choose, per event type, whether we email you in **realtime**, bundle into a **digest**, or skip the notification entirely (**off**).

> This page describes the creditor dashboard's notification settings. Debtor portal preferences are covered at the end.

## Event types

There are five event types you can configure today. The defaults are designed for most teams.

| Event               | What it means                                         | Default |
| ------------------- | ----------------------------------------------------- | ------- |
| `payment_received`  | A debtor paid (full balance or installment).          | Digest  |
| `dispute_filed`     | A debtor opened a formal dispute on a placement.      | Digest  |
| `plan_committed`    | A debtor agreed to a payment plan.                    | Digest  |
| `weekly_digest`     | Monday-morning roll-up of activity in the prior week. | Digest  |
| `monthly_statement` | Heads-up email when a new statement PDF is ready.     | Digest  |

## Modes

For each event you pick one of:

* **Realtime** — one email per event, as soon as it happens.
* **Digest** — bundled into the periodic digest email.
* **Off** — no email is sent. The event is still recorded in the audit log.

## Channels

Today the only delivery channel is **Email**. Slack and SMS channels are planned but not yet available — the UI shows them as a single-option dropdown for now.

There is no in-app notification bell or per-event recipient routing in the product today. The email goes to the address on your Clerk account.

## How to change

1. Sign in to the dashboard.
2. Go to **Settings → Manage notification preferences**.
3. For each event, pick a **Mode** and (eventually) a **Channel**. Changes save automatically.

Every change is captured in your audit log as a `notification.settings_updated` event.

## Quieting noise

If you're getting too many notification emails:

* Move noisy events (typically `payment_received`) from **Realtime** to **Digest**, or **Off** entirely.
* Keep `dispute_filed` on **Realtime** — disputes pause collection and are time-sensitive.

## Notifications and the audit log

Even if a notification mode is **Off**, the underlying event is still recorded in the audit log. Notifications control what gets pushed to your inbox, not whether an event is recorded.

## Webhooks

A single outbound webhook URL can be set under **Settings → Webhook URL** on the dashboard. We POST status-change events to that URL signed with HMAC-SHA256. There is no per-event endpoint registration or webhook test flow yet — it's one URL or no URL.

## Debtor portal notification preferences

Debtors don't have a notification settings panel of their own today. To stop contact entirely, debtors use the cease-contact flow described in [How to stop contact](/for-debtors/compliance-and-rights/how-to-stop-contact.md). A cease-contact is binding and is much stronger than a notification preference.

## TODO

* Screenshot: notification settings page with the per-event grid.
* Update once additional channels (Slack, SMS) ship.

***

Last reviewed: 2026-05-24 by Customer Success.


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://help.moderncollections.io/account-and-settings/managing-notifications.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.