> ## Documentation Index > Fetch the complete documentation index at: https://docs.member.dev/llms.txt > Use this file to discover all available pages before exploring further. # Notifications in the admin > Read the open alerts for your team, filter them by Payments or Emails, and follow each one to the page where you can fix it. The **Notifications** page in the admin lists problems the system could not fix on its own, such as a Stripe product that was archived or a hub's onboarding emails that paused. It is a read-only list of your team's open alerts. This is different from the member-facing [Notifications inbox](/guides/notifications-inbox), which delivers activity alerts to the members of a hub. ## Who can see it Only the team owner can see alerts. Anyone else who opens the page sees **Only the team owner can see notifications** and "Ask the owner of this team to check these alerts." ## Read the list The page is headed **Notifications**. Under it, a **Needs you** tab shows the number of alerts loaded. Alerts are grouped under three headings, in this order: **Payments**, **Emails**, and **Other**. A heading is left out when it has no alerts. Each row shows: * What happened, in plain words, as the row's title, and a short explanation of what it means. * Where it happened: the hub's name, or **All hubs** when the alert is not tied to one hub. If the hub is not in your team's loaded hub list, the row says **A hub**. * The date and time it was raised. * A button that takes you to where you can fix it. When there are no open alerts, the page shows **All caught up** and "When something breaks that we can't fix for you, it shows up here." with a **Go to Home** button. **Go to Home** opens the **Hubs** page. While the alerts load, the page shows placeholder rows. If they fail to load, it shows **Couldn't load notifications**, "Check your connection and try again.", and a **Retry** button. If a refresh fails after alerts have loaded, a notice above the list says "We couldn't refresh your alerts." with **Retry**, and the last loaded alerts stay on screen. ## Narrow the list The page has no filter control. A link to `/notifications?filter=payments` or `/notifications?filter=emails` narrows the list to one category. A strip at the top then says "Showing payments only." or "Showing emails only." with a **Show everything** button that removes the filter. Any other `filter` value is ignored. Filtering happens in your browser, over the alerts that have been loaded. When a narrowed list has no match yet, the page looks through more batches of alerts for you, as described in [Older alerts](#older-alerts), and shows **All caught up** only after everything has been checked. ## Fix an alert The button on each row opens the page that can resolve it: | Alert | Button | Opens | | - | - | - | | A Stripe or checkout problem on a hub | **Open payments** | That hub's **Payments** page. | | Onboarding emails paused for a hub | **Open automations** | That hub's **Automations** page. | | A contact created from a Stripe payment | **Open contacts** | **Contacts**. | Any alert from the checkout module that names a hub gets **Open payments**, even when its type is not in the table above. The alert then shows the type's name as its title, except `sync_failed_*` alerts, which are titled **Stripe sync failed**. If the destination page is not available yet, the button falls back to the nearest page that is. A hub page falls back to **Open hub**, and **Contacts** falls back to **Open hubs**. Payment and paused-drip alerts that name no hub, and alert types the admin does not recognize (other than unlisted checkout alerts that name a hub, above), show no button. The contact-created alert needs no hub and keeps **Open contacts**. ## Older alerts The page loads your newest alerts first. While older ones remain, a strip says "Showing the newest alerts." with a **Load older alerts** button. Select it to load the next batch. When you narrow the list with `?filter=` and nothing matches yet, the page keeps looking through older batches on its own, for a limited number of batches, and shows placeholder rows meanwhile. If it stops before finding a match, it shows **No matches in the alerts checked so far**, "Older alerts have not been checked yet.", and a **Load older alerts** button. Select it to keep looking. The page does not claim a category is empty until it has checked everything. If loading older alerts fails or stops advancing, a strip says "We couldn't load older alerts. Some alerts may be missing." with a **Retry** button. When no alert is showing, the page instead shows **We couldn't load older alerts.** with "Some alerts may be missing, so we cannot say there are none." and **Retry**. ## What you cannot do yet There is no way to dismiss, mark as fixed, or mark as read an alert. The list shows open alerts only. There is no **Preferences** tab, so you cannot choose which alerts reach you. ## Related * [Hub Home in the admin](/guides/admin-hub-home): shows the open alerts for a single hub. * [Getting started in the admin](/guides/admin-getting-started) This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.