Documentation menu
Dashboard & analytics
Managed runners
Team & notifications
Billing & plans
Workflow files
Notifications
Every notification Latchkey can send, the delivery channels, severity tiers, and how to tune them per event type.
In short
- 17 event types across Critical, Important, and Informational tiers.
- Channels per event: email, Slack, and browser push; informational events use a weekly Digest toggle, and every notice also lands in the in-app bell, except a repeat inside its cooldown.
- Most events start off; email is on for the trial, runner-block, free-tier, spend-limit, bonus-grant, bonus-offer and code host permission notices, and Slack for "Managed runner blocked" and "Free tier running out". Levels speed up tuning.
Settings, Notifications tab, Channels. Per-event overrides opens to a matrix of the 17 notifications, each with its level, critical, important or everything, and a box for Email, Slack and Browser, except Bonus runner minutes lapsing and Slack notifications stopped, which read Bell only; Browser is not enabled, so its boxes are disabled. The summary reads 7 overrides. Slack is turned on for Pipeline is broken: the summary reads 8 overrides and Save changes and Discard appear. After Save changes, the buttons give way to the line Preferences saved.
Latchkey notifies you when something needs attention: a pipeline breaking repeatedly, an AI scan waiting for your approval, your trial or free minutes running out, or new insights worth reviewing. Configure everything in Settings, Notifications.
Channels#
Every notice also lands in the in-app notification bell, beside the workspace menu at the head of the sidebar, regardless of channel settings. Two exceptions: a repeat inside its cooldown writes nothing at all, the bell included, and the spend limit notice, the code host permissions notice, the bonus-minute offers and the bonus minutes added for keeping your plan reach owners and admins only. The panel opens under a "Notifications" header with your unread count, Mark all read clears the backlog in one click, and the footer keeps expectations straight: "Showing the last 7 days · Manage preferences in Settings".
Severity tiers and defaults#
Event types are grouped into three tiers: Critical, Important, and Informational. Most channels start off by default, with these exceptions: email is on for "Trial ending soon" and "Trial expired", so an expiring trial never passes silently; email and Slack are both on for "Managed runner blocked" and "Free tier running out", because nobody opts in to a notice about compute they do not yet know has stopped; email is on for "Spend limit", for the same reason; email is on for "Bonus runner minutes added" and "Bonus runner minute offers", because an offer with a deadline cannot wait for someone to find the toggle; email is on for "Code host permissions not accepted", because nobody opts in to a notice about a state they do not know exists; and the informational-tier weekly digest is on, so you get a weekly summary without opting in. Runner blocks caused by a repository that is not enabled, or by an expired trial, stay off until you turn the event on. "Bonus runner minutes lapsing" and "Slack notifications stopped" reach only the bell, with no email, Slack or browser channel. Email and Slack defaults are set per event type; browser push starts off for every type and the digest is on for the informational tier, and every channel can then be switched per event in the matrix. Each channel card (Email, Slack, Browser) takes one level, and in the matrix, titled Per-event overrides, master toggles flip a whole tier for one channel at once.
The noisier types also carry their own frequency caps: "Managed runner blocked" sends at most once per day, and not for the free allowance once the month's "Free tier running out" notice has gone out; "Free tier running out" sends at most once per day at 80% and once per calendar month at 100% on a workspace with no card, and once per calendar month per threshold on a subscription; "Bonus runner minutes lapsing" fires once for each addition of minutes and use-by date, a week before that date; "Slack notifications stopped" fires once each time Slack stops accepting messages; "Code host permissions not accepted" fires at most once in 90 days for each connection and each change to what it has accepted or to what Latchkey requires; and "Pipeline is broken" fires at 7 consecutive failures and escalates once more at 20 rather than pinging on every red run. The first notification carries all the signal; repeats would only train you to ignore the channel.
A Managed runner blocked event, level critical, says a managed runner could not start because of your subscription or usage limits. It first reaches the 24-hour cooldown for this type, which is checked before anything is written; nothing was sent in the last 24 hours, so it goes on. The in-app bell gets a row for every member, ana, ben and chris, whatever their channels. Email follows each member's setting or the type's default, which is on: ana and ben are sent one, chris has turned email off. Slack, on by default for this type, gets one post in the connected channel. Browser push goes only where a member turned it on: ana gets one, ben and chris do not. The same event comes again the same day: the cooldown finds one sent within 24 hours and stops it, and nothing is written, no bell row, no email, no Slack post, no push.
What can notify you#
| Notification | Fires when | Tier |
|---|---|---|
| Pipeline is broken | 7 or more live runs in a row fail on Latchkey runners in a repository (a trial run never counts, and a live run counts by its live pipelines alone); escalates once more at 20 | Critical |
| Scan failed | The AI scan did not complete; retry from the runners page | Critical |
| AI scan runner build did not finish | Building the AI scan runner image failed; tap to retry | Critical |
| Managed runner blocked | A managed runner could not start because of your subscription or usage limits; at most once per day, and not for the free allowance once the month's "Free tier running out" notice has gone out | Critical |
| Trial expired | Your free trial has ended; choose a plan to start runners again | Critical |
| Spend limit | Runner spend reached a notice percent you set, or the stop at your spend limit; owners and admins only, though a Slack post reaches the whole channel | Critical |
| Scan ready for review | Your AI repo scan finished and the runner config needs your approval | Important |
| AI scan runner is ready | Your AI-built runner image finished and is ready to use | Important |
| Free tier running out | You crossed 80%, then 100%, of included runner minutes; with no card on file at most once per day at 80% and once per calendar month at 100%, when Latchkey stops running jobs and holds new ones until a plan starts; on a subscription once per calendar month per threshold, where it reports metered overage instead | Important |
| Trial ending soon | 3 days or less remain on your trial | Important |
| Bonus runner minutes added | Bonus runner minutes were added to your workspace, usable until their use-by date; when they come from keeping your plan, owners and admins only, with no Slack post | Important |
| Bonus runner minute offers | An offer of bonus runner minutes for subscribing or keeping your plan, until it ends; owners and admins only | Important |
| Bonus runner minutes lapsing | Bonus runner minutes added to your workspace are still unused a week before their use-by date; once for each addition and use-by date, owners and admins only, in the bell only | Important |
| Slack notifications stopped | Slack stopped accepting messages, so Slack notifications are off until you reconnect; once each time, owners and admins only, in the bell only | Important |
| Code host permissions not accepted | An account on your code host has not accepted the permissions the Latchkey app asks for; at most once in 90 days for each connection and each change to its permissions, owners and admins only | Important |
| New insights found | The nightly scan found new savings or risks to review | Informational |
| Insight applied | An applied insight's pull request was merged | Informational |
A suggested baseline#
Because most events still start off, pick a posture deliberately rather than waiting for the alert you wish you had received. This one works for most teams:
| Tier | Suggested routing | Reasoning |
|---|---|---|
| Critical | Email, plus Slack | Act-now events: a broken pipeline, a failed scan, a blocked runner launch, an expired trial. They belong where the team looks first. |
| Important | Email; add Slack for the free-tier and trial warnings | Day-level urgency. The trial emails and the free-tier warnings are already on by default, and the free-tier warning already posts to Slack; the rest of this tier is worth putting in front of the whole team before a block happens, not after. |
| Informational | The weekly Digest toggle | New and applied insights read better in one weekly batch than as a trickle of single emails. |
Two notes on applying it. Slack routing is admin-only, while every member keeps their own email, push, and digest choices, so the baseline is really two separate decisions: the shared Slack channel and your personal channels. And browser push is best treated as personal: enable it for yourself if you are the person who acts on CI issues first, after granting permission on the Notifications settings tab.
How the weekly digest behaves#
The digest is the informational tier's home. Low-urgency events (new insights found by the nightly scan, an applied insight's pull request getting merged) roll up into one weekly email instead of arriving one at a time. That is also why informational types show a Digest toggle in the settings matrix instead of a per-event email toggle: the choice you are making is whether a type participates in the roll-up.
A suggested habit: treat the digest as a weekly review queue. Nothing in it needs same-day action, but unreviewed insights compound if nobody looks at them; a short weekly skim, with AI Insight open in the next tab, is usually enough.
Tuning your preferences#
- Each event type has per-channel toggles in the settings matrix; informational types expose a Digest toggle instead of per-event email.
- Shortcuts cover the broad changes: each channel card (Email, Slack, Browser) takes one level, Off, Critical only, Critical + Important or Everything, so Off on Email silences email in one click and Critical only keeps just the page-worthy alerts; under Per-event overrides, master toggles flip a whole tier for one channel at once, and Reset to defaults restores the standard setup.
- Nothing applies until you click Save changes; the page confirms with "Preferences saved."
- Slack settings are admin-only; members keep their personal email, push, and digest choices.
- Every notification email also links back to your notification settings, so you can turn an event off from the inbox side.
Q.01What notifications are on by default?
Most events start off, so a new workspace is quiet by design. The exceptions are email for "Trial ending soon", "Trial expired", "Spend limit", both bonus-minute notices and "Code host permissions not accepted", and email plus Slack for "Managed runner blocked" and "Free tier running out". Turn on what you want per event using the matrix, or use the channel levels and master toggles to set a baseline quickly.
Q.02Which channels can each event use?
Email, Slack and browser push, chosen per event type across the Critical, Important and Informational tiers. Informational events use a weekly Digest toggle instead of firing individually, and every notice lands in the in-app bell regardless of channel, except a repeat inside its cooldown.
Q.03How many event types are there?
Seventeen, grouped into three severity tiers. Critical events are the ones worth interrupting someone for; Informational events are better read weekly, which is what the Digest is for.