# Notifications

Koo tells you what happened in your account: deployment results, billing alerts, and account notices. Every notification lands in your in-app feed, and — kind by kind — you choose whether it also emails you and how often. Everything on this page is also available programmatically through the [Notifications API](/api/notifications).

## The notification bell

The bell in the console header is your notification feed. It shows an unread count and lists notifications newest first, covering:

- 
- 
-

To work the feed:

1. 
2. 
3.

Notifications are personal. Each member gets their own feed, and your preferences are yours alone — they apply across every account you belong to.

## Deploy notifications

Two kinds cover the deploy pipeline:

- 
-

Both go to the member who triggered the deployment. A deploy started by a [git push](/docs/deploy/deploy-from-git) has no user actor, so it notifies no one — the same is true of deploys started with an [API token](/docs/developers/api-tokens) or by Koo itself.

## Choose channel and frequency

Open your account's **Settings** page and pick **Notifications**. Each kind has two controls, and both only shape email — the feed always receives every notification, so it stays your complete history.

**Channel** decides whether the kind reaches your inbox: **Email** and **In-app + email** send an email per event; **In-app** and **Off** keep your inbox clear.

**Frequency** decides how often those emails arrive: **Immediately** emails as events happen. **Daily digest** and **Weekly digest** currently just keep a kind's emails out of your inbox — the periodic summary email hasn't shipped yet. Either way the feed is never delayed: the in-app notification still lands right away.

Every kind starts on a sensible default — deploy successes default to in-app only, deploy failures to in-app and email. You only need to change the kinds you care about.

Email is a best-effort layer on top of the feed. If an email bounces or the email provider has an outage, the in-app notification still lands.

## Some notifications always email

A few kinds ignore the channel and frequency settings and always send an immediate email:

- 
- 
-

These rows show as locked to email in the preferences screen rather than pretending to be editable.

> **Note:**
>
> These events can affect your access, your data, or your bill, so they can't be muted. Everything else fully honors your preferences.

## Community notifications (Coming soon)

When [community](/docs/showcase/discovery-and-community) notifications ship, comments on your published apps and new followers will land in the feed like any other kind, with the same channel and frequency controls.

## Slack (Coming soon)

Slack delivery will post deploy events — live and failed — to a channel of your choice through a Slack incoming webhook. You will add the webhook URL in your account settings and can disable it at any time without removing it.

Slack posts will respect your deploy notification preference: turning a deploy kind **Off** will silence Slack too.