Notifications
The notification center tells you when something in Cracken needs your attention — an operation finished, an action failed, or the agent is waiting on your approval to continue. Open it from the bell in the header. From there you can read, group, and clear notifications, and choose how each kind reaches you.
At a glance
- What it is — the bell-menu notification center that surfaces operation events and approval requests.
- When to use it — check it when the bell shows unread activity, or act on a pending approval without hunting for the operation first.
- Inputs — a level filter; per-channel, per-level delivery preferences (pop-ups, browser, email); browser permission grant for browser notifications.
- Outputs — grouped, readable notifications in the dropdown, plus delivered pop-ups, browser notifications, or emails per your settings.
- Related objects — Operations, Semi-Autonomous Policy, Automations.
- Common actions — Open, Mark all read, Filter, Act on an approval request, Configure delivery per level.
- API / tool links — UI only — no public API.
Open the notification center
Select the bell in the header. The dropdown lists your notifications newest first, grouped so repeated events from the same operation collapse into one entry with a count. The bell shows your unread count, and the dropdown header shows how many notifications are unread.
- Mark all read clears the unread state for everything currently shown.
- Opening a notification marks that group as read.
- A filter in the header narrows the list to the notification levels you care about.
Notification levels
Every notification has a level. Levels let you tune how much you see and decide which events are worth a pop-up or an email.
| Level | What it covers |
|---|---|
| Critical | High-severity events that may require immediate human attention. |
| Error | Failures, including operation failures and execution errors, that need attention. |
| Approval | Notifications that require your explicit approval before the system can proceed. These pause execution until you respond. |
| Warning | Non-critical issues — sub-operations running too long, out-of-scope browser navigation, action failures. |
| Operation | Operation state changes — created, completed, action approved or denied, sub-operation cancelled. |
| Routine | Routine system events — configuration updates, step selections, tool installations, artifact operations, scope updates. |
| Debug | Diagnostic and verbose events useful while investigating system behavior. |
Approvals
When the agent reaches an action that needs your sign-off, it raises an Approval notification and pauses that operation until you respond. You can act on the request directly from the notification rather than hunting for the operation first.
Which actions need approval is set by your realm's semi-autonomous policy — the policy decides what the agent may run on its own and what it must pause to ask about. Notifications are how those pause-and-ask moments reach you.
Choose how notifications reach you
Open Notification Settings (the gear in the notification center) to control delivery per channel and per level:
- Pop-ups — toast notifications shown in the app while you're using it. Toggle them on or off per level.
- Browser — notifications shown when Cracken is in a background tab. You grant your browser's permission once, then toggle which levels are delivered. If your browser doesn't support them or you've blocked permission, the panel tells you.
- Email — notifications delivered outside the app, per level. Email delivery depends on your tenant's configuration; if it isn't set up, the panel shows that email notifications are not configured.
Pop-up and browser preferences apply to your view; email preferences are saved per user, per tenant.
Next steps
- Semi-Autonomous Policy — decide which agent actions require an approval.
- Operations — the work that generates most notifications.
- Automations — scheduled and triggered runs that report through notifications.