Skip to main content
Ankra tells you about what happens in your organisation in two places. Notifications, opened from the bell, is everything Ankra reported: failed operations, firing alerts, agent and security notices, and the messages addressed to you. Needs you, in the sidebar, is the shorter list of what waits on a person: an approval, a fix, an alert, each with the one thing to do about it. Neither page decides who else hears about a notification. That is done by notification destinations and routes, by each alert rule’s own destinations, and by your own channels under Your account → Notifications (phone and tablet).

Notifications

The bell opens Notifications (/next/notifications): Platform and Cloud activity, with one place to review what needs attention. It has three views: Above the list you can search (Title, message or cluster), narrow by Product (Platform and Cloud, Platform, Cloud) and by Audience (Everyone, Addressed to me, Organisation), and switch on Unread only. Mark shown as read marks every notification on the page as read. Each notification’s menu has Mark as read (or Mark as unread) and Archive for me (or Restore to inbox). Summarise this page asks Ankra AI to summarise the notifications shown and say what needs attention first. Opening one notification shows its details in a side panel, with Investigate with AI under Ask Ankra. Both need access to Ankra AI; without it the panel says AI access is required to start an investigation. Notification preferences at the top of the page opens Your account → Notifications, where you choose how notifications addressed to you reach you.

For you, and for the organisation

A notification is addressed either to the whole organisation, such as a failed deployment or a firing alert, or to you personally, such as a failed pipeline run you started or pushed. Audience → Addressed to me shows only yours. Reading and archiving are yours alone. Archiving shows Archived for you. The underlying issue is unchanged., and the notification stays open for everyone else.

One notification

A notification’s own page (/next/notifications/<id>) says what happened and what to do:
  • What happened - the notification’s message.
  • AI analysis - when Ankra has analysed it, a summary, Recommended actions and Read full analysis. While the analysis is being made the section reads Analysis is being prepared. This page updates automatically.
  • How to fix it - the steps, a button to the page they name, and Ask Ankra to investigate. For a notification that cleared on its own the steps fold under If it happens again, here is how to fix it.
  • Acknowledge - records that you have seen an open notification.
  • Mute on this cluster - for a notification about a cluster. It reads Muted for you on the cluster’s name, and new notifications like it from that cluster stop showing for you, including in the critical issues email. Everyone else still gets them. Manage what you muted opens Integrations & alerts → Muted notifications, where Unmute ends it.
When several critical issues are open, Previous issue and Next issue step through them.

How notifications clear

A failed operation and the notification about it are two different records. The operation stays in the cluster’s history as failed for good (see Operations). The notification is the part that clears:
  • On its own. Ankra re-checks open notifications about once a minute. A failed-operation notification resolves once a later run of the same operation on that cluster succeeds, one about a platform resource resolves when that resource’s latest step succeeds or the resource is gone, and a GitOps failure resolves once the cluster reports itself in sync again. Resolved notifications move to History.
  • By hand. Acknowledge records that you saw it. Archive for me takes it out of your Inbox and into your History, for you only.
So a cluster that has recovered has few or no open notifications, while its operations history still lists every failed attempt.

Needs you

Needs you (/next/needs-you) collects every approval, fix and alert that waits on a person, once, with the one thing to do about it. Its title counts what is waiting. When nothing is, it reads Nothing waits on you. It groups what it finds into sections. You see a section only when your role can see what it lists, and the cost sections only when the organisation has the Cost area: An item marked Urgent comes first. A section that could not be read says so and offers Try again, so an unread section never passes for one with nothing waiting.

What the portal does not have

Notifications cannot be snoozed in the portal. To hold back an alert firing for a while, use ankra alerts triggers snooze, see Alerts. There is no list of recent Stack drafts and no dashboard layout to arrange: Home opens with a question to Ankra AI, and under it what needs you.