Notifications

The notification center

The Notifications page gathers your organization's events. Three views, picked with the tabs above the list: the Journal (the default), newest first and grouped by day, with what needs your attention at the top; the Inbox, a compact list on the left and the full detail of the selected notification on the right; By resource, one panel per project, server or account, the most urgent first. Pierrr remembers the last view you picked. Each entry carries a marker whose icon tells the kind of event and whose shape tells its severity, a title and a text written in your language, and the time. The bell in the sidebar shows a badge with the number of unread notifications, and pops a toast when a new event arrives, with a button that goes straight to the item involved.

Each entry about a specific item carries a button saying where it leads: "View deployment", "View container", "View containers", "View server", "View domain", "View invoice", "View scan", "View my usage", "View organization", among others. It opens the right page, on the right tab, and scrolls to the item, which briefly lights up so you spot it at a glance. Following it marks the notification as read. A failed deployment shows its summary and the first lines of the log, and "View full log" opens it entirely, with a Copy button; "View full message" does the same for a long text. An unhealthy container notification also gives access to the last hundred lines of its logs without leaving the page.

The bell is also available in the collapsed sidebar. The right to receive notifications is granted to the Owner, Maintainer and Developer roles, not to Billing.

Pending invitations

Invitations to join an organization show up at the top of that same page. You accept or decline them there, without hunting for the original email.

Event types

Pierrr notifies you of the key moments in your organization's life cycle:

• Deployment succeeded or failed, with the stage and the reason for the failure.
• Container unhealthy, stopped or restarting.
• Quota exceeded on one of your plan's resources.
• SSL certificate expiring soon on one of your domains.
• Security scan finished, with the number of vulnerabilities found or "No vulnerability detected", or a scan that failed.
• A workflow run failed.
• Invoice paid, or a failed payment on the renewal.
• Organization deletion requested.

The severity, info, warning, error or critical, sets the colour of the entry and also decides what goes out on the other channels.

Read and unread

Unread notifications are highlighted and counted in the bell badge. The "Mark all as read" button resets the counter, each entry can be marked individually, and following an entry's button marks it read. The same event received several times within one second shows only once.

Filtering

The Journal splits what needs a hand, what is for information, and everything. A row of pills, one per project, server or account involved, narrows the list to that resource; a second click removes it. Filters by kind of event, by severity and "Unread only" complete it depending on the view. They apply instantly to the notifications already loaded; if none matches, the page says so and offers to show everything again.

Push notifications

A banner offers to enable push notifications on the device you are using, with an Enable button and a Later button to postpone. Once accepted, you are alerted as soon as a container goes down, a deployment or workflow fails, or an organization deletion is requested, even with the tab closed. It is a browser permission: it applies to this device and this browser, and is withdrawn from their settings.

Other channels

Beyond in-app, some events are also routed to the organization's email, for example a certificate about to expire or a requested organization deletion, from a severity threshold specific to each channel. A successful deployment or a finished scan therefore stays in-app, where a critical incident follows you.