Skip to main content
Marking a notification as read removes its unread indicator while keeping the entry available in the normal list. You can read one entry by opening it or confirm a bulk action for all unread notifications addressed to your account.

​
Who can do this?

Owners, Managers, and Staff can update the read state of notifications that belong to their own authenticated user. The action does not mark another team member’s copies as read. It also does not change the underlying order, booking, rating, or system event.

​
Where

Open Notifications for the selected shop in the Management Admin App. Unread rows have a green indicator. The Mark all as read button appears only when the current shop has at least one unread entry for you.

​
Mark one notification

  1. Find the unread row.
  2. Select the row itself—not the X dismiss control.
  3. Tapp records the read state and removes the unread indicator.
  4. If the notification includes a web deep link, Tapp also opens that destination. If it has no link, you remain on the page.

​
Mark all notifications

  1. Select Mark all as read above the list.
  2. Review the confirmation, including the unread count and shop name.
  3. Select Confirm. Choose Cancel, press Escape, or select outside the dialog to leave the entries unchanged.
  4. Wait for processing to finish. The notification list and unread count refresh after success.
The bulk endpoint operates on all unread notifications for your user, not only the rows currently visible on one page. The shop name in the dialog provides context, but read state remains tied to your own notifications.

​
Platform notes

These controls are implemented in the web Management Admin App. The header preview and full page share the same notification data, so the unread count updates after the cached list is refreshed.

​
Market notes

The read workflow is identical for GB and DE shops. Dialog copy, dates, and labels follow the app language; the read timestamp is the same underlying record.

​
If the unread badge remains

Allow the request to complete, then refresh the page. Check that you opened the row rather than its dismiss button and that you are viewing the same shop. If the bulk dialog closes without the count changing, retry once; persistent failures should be reported with the shop, time, and affected notification title.