The bell icon in the top-right of your provider dashboard is your real-time feed of activity on your listings. This article explains what each notification means, how the bell behaves, and how to manage your notifications.
There are four kinds of notifications today:
| Notification | When you get it | Where it takes you |
|---|---|---|
| Sale | A customer completes a session registration | Session roster, with the new participant highlighted |
| Drop-in sale | A customer completes a drop-in date purchase | Session drop-ins tab, with the purchase highlighted |
| Cancellation request | A customer requests a refund or cancellation | Session roster, with the cancellation highlighted |
| Waitlist signup | A customer joins the waitlist on a sold-out session | Session waitlist tab |
Each notification carries the relevant context inline — participant name, session, dates, and the amount for sales — so most of the time you can decide whether to act without leaving the bell dropdown.
The red badge on the bell shows your unread count. If you have 10 or more unread notifications, it shows "9+" rather than the exact number.
Click the bell to open the dropdown. The most recent 10 notifications appear first, and the list scrolls infinitely as you go back. Unread notifications have a subtle blue background; read notifications are white.
You can mark a single notification as read by clicking it (which also navigates you to the relevant page), or mark everything as read at once with the Mark all as read button at the top of the dropdown.
The unread count refreshes about once a minute while your dashboard tab is open and active. When you switch away from the tab the refresh pauses; when you come back it resumes immediately. This keeps the bell up to date without burning resources in the background.
If you need to be certain you're seeing the latest state, reload the page — it forces a fresh read.
The bell is in-app only. Enrichment.kids does not send you an email for every sale, cancellation request, or waitlist signup — that would bury you in inbox noise. The bell is the "is there anything new" surface; the dashboard reports (Sales Report, Payout Report, roster) are the durable records.
Transactional emails that do get sent automatically:
None of these go to you as the provider — they go to the customer. Your visibility is the bell and the dashboard.
If your organization has more than one user on the account, each user has their own bell. Every event creates a separate notification for every user in the org. Reading one user's notification doesn't mark it read for the others.
This is intentional — it means your front-desk staff and your director can each manage their own notification queue without stepping on each other. A practical implication: if you're trying to confirm whether a teammate has handled a cancellation request, look at the relevant roster page rather than the bell. The bell only tells you about your read state.
I didn't get a notification for a sale that happened. Where is it?
First check whether the badge count is up to date — if your tab was inactive for a while, the count refreshes when you return to it. If the sale appears in your Sales Report but no notification ever appeared in the bell, contact [email protected] with the order number and we'll investigate.
Can I turn off certain notification types?
Not currently. All four notification types are always on for every provider user. If you don't want to act on a particular notification, you can mark it read and move on.
Can I get notifications by email or text instead?
Not at this time. The bell is in-app only. If this would be useful for your operation, let us know — we track requests for additions to the notification system.
My teammate marked something as read, but it's still unread for me. Is that a bug?
No — each user in an organization has their own independent read state. See Multi-user organizations above.
How far back does my notification history go?
All notifications are kept indefinitely. Scroll the dropdown to view the full history.
The bell shows a notification but the page it links to doesn't show what I expected. What happened?
Most often this means the underlying event was reversed before you opened the notification — for example, a customer started a refund request and then cancelled it before you saw the original notification. The bell entry remains as a historical record, but the linked page reflects the current state. Contact support if this happens unexpectedly and we can confirm what occurred.