Notifications

The notification center

The Notifications page lists your organization's events, newest first. Each entry carries a severity icon, a label describing the event and a timestamp. The bell in the sidebar shows a badge with the number of unread notifications, and pops a toast when a new event arrives.

Some entries carry an action: a View button opens the screen involved (the deployment, the project, the invoice), and an unhealthy-container notification gives access to the last hundred lines of its logs without leaving the page.

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.
• 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, and each entry can be marked individually.

Filtering by severity

The Notifications page offers a severity filter above the list: All, Info, Warning, Error and Critical. Pick one to narrow the list to that severity; the filter applies instantly to the notifications already loaded.

Push notifications

A banner offers to turn on push notifications on the device you are using. Once accepted, you are alerted as soon as a container goes down or a deployment fails, even with the tab closed. It is a browser permission: it applies to that device and that browser, and is withdrawn from their settings.

Other channels

Beyond the in-app center, some events are routed to the organization's email or to a Discord channel, depending on what is configured on the instance and from a severity threshold specific to each channel. An informational event therefore stays in-app, while a critical incident follows you.