Notifications
Koo tells you what happened in your account: deployment results, billing alerts, team changes, and activity on your public apps. Notifications arrive in the in-app feed, by email, or both — you choose per event kind. Everything on this page is also available programmatically through the Notifications API.
The notification bell
The bell in the dashboard header is your notification feed. It shows an unread count and lists events newest-first, covering:
- Deploys — a deployment went live or failed.
- Billing — payment failures, plan changes, and other billing events.
- Team — invitations to an account (teams and roles).
- Community — comments on your apps and new followers (discovery and community).
- Account — data export results, account deletion notices, and location retirement warnings.
To work the feed:
- Open the bell. Unread notifications show a dot.
- Click a notification to mark it read; the unread count decreases.
- Use Mark all read to clear everything at once.
Notifications are private to you — each member of a team gets their own feed and their own preferences.
Deploy notifications
Two kinds cover the deploy pipeline:
- Deployment is live — sent when the new version is observed ready, not when it is merely applied. A slow-booting release notifies you when it is actually ready; a release that never becomes healthy never claims to be live. Defaults to in-app only.
- Deployment failed — sent when the pipeline fails: the build broke, or the rollout couldn't complete. Defaults to in-app and email.
Both go to the person who triggered the deployment. Deploys triggered by a Git push or by Koo itself don't notify anyone yet.
Like every kind, both channels are yours to change in preferences.
Email delivery
The same events can reach your inbox. Whether a kind emails you follows your preference for it: email or both sends an email, in-app or off keeps it out of your inbox.
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, so the feed is always your complete history.
Preferences
Open Settings → Notifications to choose how each event kind reaches you. Kinds are grouped by category (deploys, billing, team, community, account), and each has a delivery channel:
| Channel | Effect |
|---|---|
| In-app | Feed only |
| Inbox only | |
| Both | Feed and inbox |
| Off | Neither |
Every kind starts on a sensible default — deploy successes default to in-app only, deploy failures to both. You only need to change the kinds you care about; anything you haven't touched keeps its default.
Some notifications always email
A few kinds ignore the off setting and always send an email:
- Payment and subscription events (failed payments, plan changes, refunds, an expiring payment method).
- A scheduled deletion of your user or one of your accounts.
- A finished data export.
- A location retirement notice that requires you to move your apps.
These appear locked to email in the preferences screen rather than pretending to be editable.
These events can affect your access, your data, or your bill, so they can't be muted. Everything else fully honors your preferences.
Slack Coming soon
Slack delivery will post deploy events — started, 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 the sink at any time without removing it.
Slack posts will respect your deploy notification preference: setting deploy kinds to off will silence Slack along with the feed and email.