Notifications
Olympusx AI tells you about events that need you, or that you would otherwise have to watch a page for: a model that finished deploying, a budget nearly spent, an agent waiting for an approval. Notifications appear in the console.
Who can open it
Section titled “Who can open it”Every role. Each person sees only the notifications addressed to their role in their tenant. A platform admin also sees the platform’s own notifications, which no tenant user sees.
What raises a notification
Section titled “What raises a notification”| Category | Event | Severity | Who receives it | Opens |
|---|---|---|---|---|
| Agents | An agent’s tool call is held for approval | Warning | Admin, Reviewer | The approval (or the approvals list, when one run held several calls) |
| Billing | A tenant, project, key or model budget passes one of its alert thresholds | Warning | Admin | Govern › Keys and budgets, Budgets tab |
| Billing | A budget is spent and requests are refused | Error | Admin | Govern › Keys and budgets, Budgets tab |
| Account | An API key is revoked | Warning | Admin | Govern › Keys and budgets |
| Deployments | A model is deployed and callable | Success | Admin, Builder, Auditor, platform admins | Build › Models in that tenant |
| Deployments | A model failed to deploy | Error | Admin, Builder, Auditor, platform admins | Build › Models in that tenant |
| Deployments | A model import finished or failed | Information or warning | Platform admins | Model serving › Model registry |
| System health | A platform component stops responding (three failed checks in a row), and again when it recovers | Error, then success | Platform admins | Infrastructure › System health |
| Platform | A tenant is created | Information | Platform admins | Customers › Tenants |
Each event notifies once. A budget threshold notifies once per budget period, not on every check.
When a held tool call is answered, its notification changes: the title says the call was approved or rejected, and its severity drops to information, so a decided approval no longer looks like work to do.
What you see
Section titled “What you see”The bell
Section titled “The bell”The bell sits in the console header. Its badge shows how many unread notifications you have, up to 99+. The count refreshes every 30 seconds.
Select the bell to open the notification panel:
- Mark all read, at the top.
- Your 20 most recent notifications, unread ones marked Unread. Each shows its severity, title and one line of detail, and is a link to the page it is about.
- View all, which opens the notification history.
Pop-up alerts
Section titled “Pop-up alerts”When a new warning or error arrives, the console shows it as a short pop-up alert on whatever page you are on, with Open to go to what it is about. At most three alerts appear for one batch of arrivals. Information and success notifications do not pop up; they wait in the bell.
The notification history
Section titled “The notification history”View all in the panel opens Notifications, the full history. You reach the page from the bell, or from the command palette.
- Mark all read, at the top right.
- Category, a dropdown with All categories and each category in the table above.
- Unread only, a toggle.
- The Notification history table, newest first, with a search field (Search notifications) and a Severity filter (Error, Warning, Success, Information):
| Column | What it shows |
|---|---|
| Status | Unread, or Read. |
| Severity | Error, warning, success or information. |
| Category | The category. |
| Notification | The title, as a link to what it is about, and a line of detail. |
| Received | When it arrived. |
| Actions | Mark as read, on unread rows. |
The category, unread and severity filters are kept in the page address, so a filtered history survives opening a notification and coming back, and can be shared as a link.
With no filter applied and nothing in your history, the page says Nothing to catch up on. With a filter applied and nothing matching, the table says it has no results and keeps its filters visible.
What you can do
Section titled “What you can do”Open a notification
Section titled “Open a notification”- Select its title in the panel or the history.
- The console opens the page it is about and marks the notification read.
Mark notifications read
Section titled “Mark notifications read”- One: select Mark as read on its row.
- All: select Mark all read in the panel or on the history page.
Stop a category reaching the bell
Section titled “Stop a category reaching the bell”- Open Your profile from the user menu.
- Under What reaches the bell, switch the category to Muted.
A muted category no longer appears in the bell or its count. Nothing is deleted: the history still lists it when you pick that category in Category, and the page says the category is muted, with a link to change it. See Profile and preferences.
Limits
Section titled “Limits”| Limit | Value |
|---|---|
| Notifications kept | 90 days, then deleted |
| Shown in the bell panel | 20 most recent |
| Shown on the history page | 200 most recent; the page says so when there are more, and filtering by category or unread reaches older ones |
| Badge refresh | Every 30 seconds |
| Pop-up alerts per arrival | 3 |