Choose which notifications you get
Turn on notifications on your phone or browser, pick instant, hourly or off per app, and set quiet hours, muted apps and your devices.
Cockpitify notifies you when something happens in your app: a new sign-up, a purchase, a low balance, a project that stops answering. The team’s rules decide what can fire (see See and manage every alert). What reaches you, and on which device, is yours to choose here. Nobody else’s settings change.
Turn on notifications on your phone
Cockpitify doesn’t ask at launch. Allow notifications from the card on Home, or:
- Tap your avatar at the top to open Account settings.
- Under Notifications for you, tap Quiet hours, muted apps and devices.
- Under This phone, tap Allow.
If it says Notifications off with Open settings, they’re blocked in the phone’s settings. Tap Open settings and turn them on for Cockpitify.
Turn on notifications in your browser
The web console can send the same notifications to your browser.
- Click your avatar at the top right and open Account settings.
- Under This browser, turn on Browser notifications, and allow them when the browser asks.
You can also turn them on from the bell in the top bar. If the site’s notifications are blocked, allow them in the site settings in the address bar, then reload. On iPhone and iPad, add the site to the Home Screen first. Signing out turns them off in that browser.
Choose what you get from each app
Each app has its own choices, so a busy app can be quieter than the others.
- Phone: tap the app’s name at the top, then App settings → Notifications.
- Web: open App → App settings → Notifications.
Each category is Instant or Off. New user can also be an Hourly digest: the last hour’s sign-ups in one notification.
| Category | When it fires | Default |
|---|---|---|
| New user | Every sign-up, or an hourly digest | Instant |
| Premium and cancellations | Users who go premium, leave it or whose payment fails | Instant |
| Low balance | A service drops below its warning threshold, runs out soon or passes its budget | Instant |
| User AI limit | A user goes over the daily AI limit | Instant |
| Project status | The project becomes unreachable, and when it’s back | Instant |
| Usage drop | Active users or a feature’s use drops sharply, usage data stops, or a metric threshold alert fires | Instant |
| Event alerts | An event your team set an alert for happens, or piles up | Instant |
| Stability | A release drops under your crash-free line, Sentry sees a new error, or an EAS build or submission fails | Instant |
| Daily summary | Each morning after 03:00 UTC: yesterday’s new users, active people, premium, cash in (money paid that day), AI cost, and cash in minus AI | Off |
| Weekly insights | Monday morning: the 3–5 biggest changes of the week before | Instant |
| Setup reminders | Up to three in your first week, while a step that opens margin is missing | Instant |
To see every app at once, open Account settings → Notifications for you. Each app shows a short line such as “9 instant · 1 hourly · 1 off”; tap it to change that app.
Mute an app for a while
Muting stops pushes from one app for you only. Alerts still land in your inbox, and the rest of the team still gets them.
- Phone: Account settings → Quiet hours, muted apps and devices → Mute an app.
- Web: open the app, then App settings → Notifications → Mute <app name>.
On the web, Account settings → Notifications for you marks each muted app with Muted and shows until when.
Choose 1 hour, 8 hours, 1 day or Until I turn it back on.
Quiet hours
Quiet hours hold pushes overnight, in the time zone you pick. They still land in your inbox.
- Phone: Account settings → Quiet hours, muted apps and devices → Quiet hours.
- Web: Account settings → Quiet hours.
Turn on Quiet hours, then set From and To. A few alerts still come through: the project becoming unreachable and coming back online, and a subscriber’s payment failing.
Your devices
Your devices lists the phones and browsers that get your pushes, and when each last got one. On the web you can Add a phone with a QR code, and Remove a phone you no longer use. A removed phone gets no pushes until Cockpitify is opened on it again.
Weekly insights
Every Monday, Cockpitify picks the 3–5 most important changes of the week before: money first, then customers you may lose, growth, product use and AI cost. Small moves stay out (under $50 or 10 people), and each person gets only the lines they may see. When nothing crossed its line, nothing is sent.
Metric threshold alerts
Get notified when a weekly number gets worse: active people, new people, net revenue, new payers or trials dropping by 10, 20, 30 or 50%, or AI cost rising by that much. The last 7 days are compared with the 7 before, each rule fires at most once a week, and small numbers don’t alert (the week before needs at least 20 people or $20).
- Phone: open the Alerts page and tap “A weekly number moves the wrong way”, or open Connections → Usage tracking.
- Web: App → App settings → Notifications → Metric threshold alerts, or the row on the Alerts page.
These alerts follow your Usage drop choice.
The inbox
Tap the bell at the top to see the last 30 days of notifications from all your apps, newest first. On the phone they’re grouped by Today, Yesterday and date; tap Older to load more. On the web the bell shows the newest ones; See all opens the full list. Opening the inbox clears the badge, and tapping a notification opens the related screen.
Not getting notifications?
- Phone: check that This phone says Notifications on.
- Browser: check that Browser notifications is on in Account settings.
- Check the category isn’t Off in that app’s App settings → Notifications.
- Check the app isn’t muted and you aren’t inside your quiet hours.
- Check the rule is On on the Alerts page, and that Team push is ticked under Goes to.
- A locked app sends no notifications; see Locked apps.
- Low balance alerts fire once per threshold and re-arm only after the balance goes back up.
- If the project is paused, nothing can be detected until it wakes up. See Troubleshooting.