Reading notifications

Distinguish in-app notifications from browser alerts#

In-app notifications can be consulted in Qublo through the bell and history. Browser alerts are messages shown by the browser when permission is enabled and Qublo is open in the background. You can use history without enabling browser alerts.

Before looking for a notification, make sure you are signed in to the correct Qublo account. Then decide whether to read recent updates or find an entry in history. The bell number measures unread notifications, not failed operations.

A notification summarizes an event. To understand the complete result and act on the linked product, order or request, open its destination.

Open recent notifications#

Select Qublo’s bell to see recent updates. The badge number indicates unread notifications.

1. Read the notification’s title, summary and time.
2. Open it to reach the linked page.
3. Select View all notifications to consult history.

Opening the list does not mark all notifications as read. Opening one notification updates that notification’s read status instead.

Filter and mark as read#

1. In history, choose All, Unread or Read.
2. Select Refresh to reload the list.
3. Use Open to view the linked page, or Mark as read to change only the read status.
4. To update every notification, select Mark all as read.

Use Previous and Next to move through the pages. If a filter shows no results, switch to All.

Marking a notification as read does not complete the operation or resolve the error described: open the linked page to take action.

Enable browser alerts#

1. Open the bell and find Browser notifications.
2. Select Enable.
3. Allow notifications in the browser’s permission request.

Activation applies to the current user and browser. Alerts arrive while Qublo is open in the background.

If permission is blocked, enable it in the browser’s site settings. To stop alerts, return to the panel and select Disable. If the browser does not support the feature, consult notifications within Qublo.

Understand what changes when you read a notification#

The bell highlights unread entries. Opening the panel or going to history does not by itself change every entry’s status. When you open one notification, Qublo records it as read and navigates to its intended destination.

Mark as read is useful when you want only to update reading status while staying in the list. Mark all as read updates the overall unread count: use it once you decide you no longer need those entries as reading reminders.

If you use Dismiss in the recent panel, check the result in the list and consult history when you need to reconstruct the context. None of these actions replaces the correction required on the product or order page.

Example: finding an update you already opened#

You opened a notification and went to the linked page. Later, you want to read it again, but it no longer appears under Unread. Open View all notifications, choose Read or All and move through the pages.

Compare the summary and time to distinguish similar updates. Use Open on the correct entry if you need to return to its destination. If the list remains empty, check the filter and select Refresh before changing accounts or repeating the original operation.

This example concerns notification status: it does not mean that the associated operation should be performed again. To decide whether to repeat anything, read the result on the destination page.

If the browser does not show alerts#

1. Open the bell and read the Browser notifications status.
2. If the feature is disabled, select Enable and respond to the browser request.
3. If blocked permission is shown, open the browser’s site settings and allow notifications.
4. Return to Qublo and check that activation is reported for this user and browser.

The setting is not a promise of notifications on every device: another browser has its own permissions and activation. Qublo must remain open in the background for the workflow described.

If the feature is unsupported or you prefer not to grant permission, keep using the in-app bell and history.

Handle errors and routine checks#

If loading shows an error, use Refresh and wait for the result. Do not mark everything as read just to try reloading the list: the actions have different purposes. If Open does not reach the expected page, keep the notification summary and the message shown.

A useful routine is to read Unread first, open entries requiring action and use Read to find updates already consulted. Always check the linked page’s data before acting.

For a persistent alert problem, tell support the account, browser, permission shown and when you noticed the issue. You do not need to attach a buyer’s personal data if the fault concerns the notification panel.