> ## Documentation Index
> Fetch the complete documentation index at: https://help.usetapp.io/llms.txt
> Use this file to discover all available pages before exploring further.

# Dismiss a notification

> Remove an individual notification from your visible list while preserving the underlying event.

Dismiss a notification when you no longer need it in your visible list. Dismissal soft-deletes the notification for your user; it does not undo the event described by the message and is different from merely marking it as read.

## Who can do this?

Owners, Managers, and Staff can dismiss notifications assigned to their own authenticated account. You cannot dismiss another team member’s copy. Dismissal does not cancel an order, reverse a payment, reject a booking, restore a menu item, or change any other product record.

## Where

Open **Notifications** in the Management Admin App after selecting the intended shop. Each row has an **X** control on its right. Its accessible label includes the notification title so you can identify the intended entry.

## Dismiss one entry

1. Verify the shop and notification title.
2. If you may need the details later, open the related workflow first or retain the title and timestamp. The current interface does not show a restore control.
3. Select the **X** on the notification row. Selecting the row itself performs a different action: it marks the entry as read and may follow a deep link.
4. Tapp requests a soft delete and refreshes all notification lists after success. The entry disappears from the normal page and header preview.

Use **Mark as read** instead if you want to keep the record visible while clearing its unread indicator. Use dismissal only for individual entries; there is no bulk-dismiss control on the current Notifications page.

## Platform notes

The web app sends a delete request for the chosen notification ID. The API validates the authenticated user and changes the notification to the deleted state instead of removing the underlying business event. Normal list requests exclude deleted entries.

## Market notes

The behavior is the same in GB and DE. Localized text may differ, but dismissal applies to the same user-level notification record and has no country-specific business effect.

## If the entry does not disappear

Wait for the request and list refresh, then reload the page. Confirm that you selected the **X**, not the row. If the notification returns, do not repeatedly dismiss unrelated entries; record its title, time, selected shop, and your role for support. If you dismissed the wrong entry, use the underlying product area to verify the actual order or booking state because the notification list is not the source of truth for that workflow.

## Related articles

* [View and filter notifications](/en/notifications/view-and-filter-notifications)
* [Mark notifications as read](/en/notifications/mark-notifications-read)
* [Understand notification types](/en/notifications/understand-notification-types)