Notifications

Notifications are how Lumio nudges you about things that need your attention: pending account invites, someone mentioning you on the Ideas Hub, a recap when a stream ends, and developer-programme events. They live in a dropdown under the bell icon in the dashboard's top bar — no inbox, no separate page, just a quick glance and an inline action.

Where to find it

The bell icon sits in the top-right corner of the dashboard, right next to the Streamer Mode shield toggle. (Your account switcher and avatar live in the sidebar, not next to the bell.) If you have unread notifications, a small badge shows the count (1, 2, … up to 99+). Click the bell to open the dropdown.

If there's no badge and the dropdown says No notifications yet., there's genuinely nothing — the dropdown doesn't hide anything you haven't dismissed.

Quick start

1. Click the bell icon in the top-right.
2. Unread items are highlighted with a subtle accent background.
3. Click the check icon on any item to mark it as read.
4. Click the double-check icon in the dropdown header (Mark all as read) to clear the badge.
5. If a notification has buttons (e.g. Accept / Decline for an invite), click one to run the action inline — no separate page needed.

That's the quick path for acting on notifications. For controlling how and where notifications are delivered, see Notification Preferences below.

The bell dropdown in depth

When you open it, you see:

• A header with the title Notifications and two icon buttons: a double-check (Mark all as read), shown only while something is unread, and a bin (Delete all notifications), shown whenever the list isn't empty.
• The most recent 10 notifications, ordered newest first.
• Each row shows: title, optional message (lighter text), timestamp (localized to your browser), an inline check button while it is unread, and — if the notification is actionable — one or more action buttons.
• A scrollable list: scroll inside the dropdown to see the full ten.

The dropdown closes when you click outside it, or when you click the bell again.

Polling and freshness

The bell polls for notifications every 30 seconds in the background, even when the dropdown is closed. That means:

• A new notification can take up to 30 seconds to appear after the backend creates it.
• The badge stays roughly in sync without any manual refresh.
• Polling runs silently; if a request fails (network blip, API restart), the UI just keeps the last-known state and tries again 30 seconds later.

If you need a fresh view right now, reload the page — opening and closing the dropdown doesn't trigger a fetch by itself, but the next polling cycle is at most 30 seconds away.

Notification types

Notifications today include:

• Account invites — Someone invited you to join their account. These carry Accept and Decline action buttons. If the inviter cancels before you act, the entry turns into an "invitation was revoked" notice.
• @mention in an idea — Someone mentioned you in a comment on the Ideas Hub. A View button takes you straight to the idea.
• Stream summary — A recap for the account owner after one of your streams ends, delivered in the bell and (by default) as an email with a viewer chart. Sessions shorter than five minutes are skipped, so test streams don't generate one.
• Developer programme events — The outcome of your developer application, extension lifecycle events (created, version submitted / approved / rejected / published, extension suspended), extension access grants, tester invitations, and developer-team invites and membership changes.

Each notification carries a machine-readable type on the backend, but you interact with it through its human-readable title and message — the type is only relevant when triaging bugs with support.

Platform connection problems are not delivered through the bell. A failed token refresh surfaces as a banner at the top of the dashboard instead — see Connections.

Notification Preferences

Open Dashboard → Settings and scroll to the Notifications section to control how each notification type is delivered to you.

Preferences are tied to your user account, not to a channel — they are available no matter which entry is selected in the account switcher, including your personal profile, and one setting applies across all your channels.

The types are grouped by category:

Category	Type	Configurable
Account	Invites	No — always delivered
Ideas Hub	@Mentions	Yes
Stream	Stream summary	Yes

For every configurable type you can choose one of four options:

Setting	What happens
Off	No notification of any kind is sent
In-App	A notification appears in the bell dropdown only
Email	An email is sent, with no bell-dropdown entry
In-App + Email	A notification appears in the bell dropdown and an email is sent

The default for all types is In-App + Email.

Invites are system-critical: they are always delivered in both channels and their setting is locked, so they appear in the bell dropdown regardless of your preferences.

Changes take effect immediately; there is no save button.

Actions

Actionable notifications have one or more buttons below the message. The most common example is the account invite:

• Accept — adds you as a member of the inviting account, switches your active account to it, and reloads the dashboard.
• Decline — deletes the invite, so the link in it can no longer be used.

Clicking an action disables both buttons while the server processes the request. If the action fails (e.g. the invite expired between the time you saw it and clicked, or you are already a member), the buttons re-enable — try refreshing and check Dashboard > Members > Invites instead.

Once a notification has been acted on, the buttons disappear. The notification stays in your list (now read and acted) so you have a trail of what happened.

Permissions

Notifications are always scoped to you as a user, not to an account. That means:

• Switching accounts does not change what you see in the bell — your pending invites, mentions, etc. are yours.
• No RBAC permission is required to view or interact with your own notifications; the backend only checks that the notification belongs to you.
• Notifications are private to your own signed-in session. A popout token cannot read them or act on them, even though it belongs to the same user.

Capability	Required Permission
See your own notifications	(none — tied to your user)
Mark one as read	(none — your own)
Mark all as read / delete all	(none — your own)
Execute an action button	(none — accepting or declining an invite is a user-level decision, validated against the invite itself)

Tips & best practices

• Clear invites promptly. Accept or decline them rather than letting them pile up. An invite you decline is deleted and can no longer be used.
• Watch the dashboard banners for connection problems. A platform whose token refresh failed shows up as a banner, not a bell notification. Click through to Connections and reconnect.
• Don't rely on notifications for real-time events. Chat messages, follows, subs, etc. flow through the WebSocket event pipeline, not the notification bell. Use Dashboard > Events or the overlay Event List for stream-time activity.
• Mark all as read after triage. It keeps the badge honest. If you leave read notifications around, the badge won't come back — but fresh unreads will still show up.

Troubleshooting

Badge shows a number but the dropdown is empty. The dropdown shows the 10 most recent notifications regardless of read state, while the badge counts every unread one. With more than 10 notifications, older unread ones aren't visible here — use Mark all as read to reset, or triage the visible ones first.

I accepted an invite but nothing happened. Accepting switches your active account to the one you joined and reloads the dashboard. If it didn't, check Dashboard > Members for your new membership and switch via the account switcher. The bell notification stays (acted state) as a receipt.

Invite action buttons are disabled and stuck. The request is in flight. Wait a few seconds; if they stay disabled, the action likely failed — refresh the page and the updated state will load via the next poll.

The bell doesn't appear at all. You're probably looking at a page outside the authenticated dashboard (e.g. /overlay/..., /login), or at a fullscreen editor page that hides the top bar. The bell is part of the dashboard shell and only renders when you're signed in.

I want to disable or reduce notifications. Open Dashboard → Settings and set the configurable types to Off, In-App (no email), or Email (no bell entry). Account invites cannot be disabled.

New notification didn't appear for ~30 seconds. Expected. Polling is on a 30-second cadence. Reload the page to fetch immediately.

Related docs

• Members — sending and managing invites, which is where most of the invite notifications originate.
• Connections — reconnecting a platform after a token refresh failure.
• Roles and Permissions — understanding the actions behind notification buttons.
• Ideas Hub — @mentions in idea comments that trigger mention notifications.