> For the complete documentation index, see [llms.txt](https://docs.countercyclical.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.countercyclical.io/notifications/channel-preferences.md).

# Channel Preferences

Control which types of workspace activity can reach you through Email, In-App, and Push.

Channel Preferences provide granular controls beneath the account-level Methods settings. This lets you keep a delivery method enabled globally while disabling it for specific kinds of activity.

See also [Slack Notifications](https://docs.countercyclical.io/notifications/slack-notifications) and [Custom Alerts](https://docs.countercyclical.io/notifications/custom-alerts).

### How Channel Preferences Work

Go to [**Settings › Notifications › General**](https://dashboard.countercyclical.io/settings/account/notifications/general) and scroll to **General**.

The preference matrix contains three delivery columns:

| Channel    | Purpose                                          |
| ---------- | ------------------------------------------------ |
| **Email**  | Deliver the selected event to your email address |
| **In-App** | Surface the event inside Countercyclical         |
| **Push**   | Deliver the event through supported push clients |

A checked box enables that event for the corresponding channel. Clear the box when you do not want that event delivered through that method.

Parent resource rows can be expanded to expose more specific notification types.

### Workspace Notifications

The **Workspace** category includes account- and workspace-level activity such as:

**New Workspace Members** — Notifies you when a member is added to a workspace where you are an Admin or Owner.

**Custom Alerts** — Notifies you when a governed custom Alert matches records you can access.

Each can be configured independently across Email, In-App, and Push.

### Resource Activity

Resource categories expose notification preferences appropriate to that resource.

For resources such as **Folders**, **Investments**, **Memos**, **Pipelines**, **Dashboards**, and **Lists**, available events can include:

* **Activity** — lifecycle and content changes to a resource you subscribe to.
* **Comments and Replies** — new comments or replies within a subscribed resource.
* **Mentions** — someone uses your handle within the resource.
* **New Collaborators** — someone is added as a collaborator to a resource you follow.

The exact events available depend on the resource type.

### Task Notifications

Tasks include additional notification types because they can represent assigned work and deadlines.

Available Task preferences shown include:

**Activity** for lifecycle and content changes; **Comments and Replies** for discussion activity; **Assignments** when responsibility for a Task is assigned to you; **Review Requests** when you are asked to review a Task; **Mentions** when your handle is used; **Due Soon** when a Task you own, are assigned, or review is due within 24 hours; and **Overdue** when one of those Tasks becomes overdue.

Each event can be independently enabled for Email, In-App, and Push.

### Other Resource Types

The notification matrix also includes additional workspace resource types such as **Reports**, **Report Components**, **List Views**, and **Teams**.

Some resource types may show unavailable or disabled channel controls. Where a checkbox is unavailable, that resource/event combination cannot currently be configured for that delivery channel from this page.

For example, the interface shown has disabled controls for **Reports**, **Report Components**, and **List Views**, while configurable resources such as Lists and Teams expose active channel controls.

### Parent and Child Preferences

Each resource category has a top-level row and can be expanded to reveal its individual events.

Use the parent category to understand or control the resource's notification configuration, then use the individual event rows when you need more granular preferences.

This structure makes it possible to keep notifications enabled for an important resource while suppressing event types you do not need.

### Channel Availability

Channel Preferences operate within the channels enabled under **Methods**.

{% hint style="info" %}
If you disable Email, In-App, or Push at the top of the Notifications page, that method is removed from the effective notification configuration even if individual event preferences were previously selected for it.
{% endhint %}

For predictable notification behavior, configure the page in this order: first enable the delivery methods you want under **Methods**, then configure the events you want through each method under **Channel Preferences**.

#### Related Pages

{% content-ref url="/pages/k46Q39VGkcko4Ci0KvVX" %}
[Slack Notifications](https://docs.countercyclical.io/notifications/slack-notifications.md)
{% endcontent-ref %}

{% content-ref url="/pages/OKDqbPxLj9iLJJNg9nuF" %}
[Custom Alerts](https://docs.countercyclical.io/notifications/custom-alerts.md)
{% endcontent-ref %}

{% content-ref url="/pages/PBR4nKqFlzVTQwXkn0Y6" %}
[Email, In-App, & Push Channels](https://docs.countercyclical.io/notifications/email-in-app-and-push-channels.md)
{% endcontent-ref %}
