Notifications
Read every alert in the Notifications Center, mark it read or open it, and choose which classes of alert reach your email and your linked chat.
By the end of this page you will know where every alert Zuse Bifrost sends you is kept, how to work through the Notifications Center, and how to decide which kinds of alert reach your email and, once linked, your chat.
An alert is one thing the workspace tells you: a story waiting for your approval, a token minted on your account, an incident opened on a project you follow. Every alert belongs to a class, lands in your Notifications Center, and is delivered to the destinations you chose for that class.
The Notifications Center
The Notifications Center entry sits at the top of the sidebar, under the logo. It carries the number of alerts you have not opened and pops out the newest eight; press one to go where it points, or the tick to Mark All as Read. The number moves the moment an alert arrives, without reloading.
Open Notifications Center is the full page: how many are unread, how many there are, when the last one arrived, and every alert grouped by day in your timezone, newest first.
| Control | What it does |
|---|---|
| All / Unread / Read | Narrow the list to what you have or have not opened. |
| Class | Show one class of alert, such as Approvals or Security. |
| Search | Find words in an alert's title or body. |
| Open | Mark the alert read and go where it points. |
| Mark as Read | Mark it read and stay. |
| Mark All as Read | Clear the unread count in one go. |
| Notification Settings | Jump to the destinations grid described below. |
An alert that points nowhere, such as a notice about something already gone, shows no Open button.
Choose where alerts reach you
- Open Account Settings → Notifications. The Telegram card at the top links your account to the bot; Telegram describes it.
- The Alert Destinations grid lists one row per class and one switch per destination: your Email, and your Telegram chat once it is linked.
- Switch a cell on to have that class delivered there, off to stop. The email's Incidents, Security and AI budget cells are locked on.
- Press Save Changes.
Until you change the grid you are on the default: every class reaches your linked chat when you have one, and email carries whatever nothing else does. Switching every cell of a destination off keeps it in the grid and sends it nothing, so the next alert never falls back on it by surprise.
Email is the safety net. A class that no other destination carries is mailed, and the three critical classes are mailed whatever you pick, because they arrive precisely when the chat you would otherwise read them on may have stopped working.
The classes
| Class | What it covers |
|---|---|
| Approvals | Something waits for your decision, and the decisions made on what you submitted. |
| Assignments | Work assigned to you, reassigned, or due soon. |
| Mentions | Someone named you in a comment or an update. |
| Planning | Epics, stories, requirements and rules created or changed on your projects. |
| Sprints | Sprints planned, started and closed, and scope that changed mid-sprint. |
| Code | Branches, commits and pull requests linked to your items. |
| Testing | Test runs started and completed, failed executions and new defects. |
| Releases | Releases planned, frozen, approved, published and rolled back. |
| Deployments | Deployments queued, finished and failed on the environments you follow. |
| Incidents | Incidents opened, updated, breached and resolved, with the public status line. Always mailed. |
| Support | Support tickets raised, answered and waiting on you. |
| Security | Sign-ins, passkeys, two-factor changes and tokens minted. Always mailed. |
| Digest | Your Monday project digest, and an alert when a project breaks pattern. |
| Onboarding | Nudges to finish setting up your projects. |
| AI budget | The team's AI budget nearing or reaching its monthly cap. Always mailed. |
The classes exist from the first day so your choices are kept as each phase of the product lands; today the Security class is the one that fires, when a personal access token is minted on your account.
All the fields
Emails you cannot opt out of
A few emails go out regardless of the grid because they are how you get into, or back into, your account: the invitation that creates it, verification links when you change your address, password reset links, and the three critical classes above.
What happens next
Every alert writes one entry in your Notifications Center as it is sent, whatever else it does. The entry carries the alert's title, one line of context, its class and the page it points at, so an alert from a year ago reads like one from today. The same inbox and the same grid are readable by integrations through the REST API and by agents over MCP as those surfaces land.
Permissions
| Action | Who may do it |
|---|---|
| Read and mark your alerts | You, on your own account |
| Change your alert destinations | You, on your own account |
Frequently asked
Related
- API tokens: the first alert the Security class sends.
- Profile: change the email address receiving these alerts.
- Signing in: the account emails that bypass the grid.
How is this guide?
Last updated on