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. Opening the dropdown marks all unread notifications as read and clears the badge, including unread items older than the ten shown here. Items that were unread stay highlighted until you close the dropdown.
3. Read the titles and messages in your dashboard language. If a translation is unavailable, Lumio shows the notification's stored text.
4. If a notification has buttons, click Accept or Decline to act on an invite in the bell, or View / Review to open the related page.

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 a bin (Delete all notifications) 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), 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. Any other open bell in the dashboard clears its badge at the same time.

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 the badge shows unread notifications, opening the dropdown refreshes the list before marking them read. Otherwise, reload the page for a fresh view; 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. A team invite addressed to you has Accept and Decline buttons.

Titles, messages and action labels appear in the dashboard's UI language when translations are available. A notification with no matching translation, or one missing a value needed for its text, shows its stored title or message instead. User-written content, such as review notes or feedback, stays in the language in which it was written.

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 Settings → You → Notifications (/dashboard/settings/notifications) 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.

Each category is its own section with an In the app and an Email switch per type:

Category	Notices	Configurable
Security	New sign-in, 2FA on/off, authenticator app or passkey added or removed, recovery code used or regenerated, password or sign-in method changed, failed attempts	No
Account & channels	Invite; role change, removal, support identity check	Invite: no; others: yes
Data & privacy	Export ready, profile deletion scheduled, channel dissolution scheduled, reminded or cancelled	No
Stream	Stream summary, connection needs reconnection	Yes
Billing (channel owner)	Invoice paid, payment failed, plan changed, cancellation receipt	Payment failure and cancellation receipt: no; others: yes
Ideas Hub	@Mentions	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

Defaults vary by type. Security and required privacy notices use In-App + Email. New invoices also default to In-App + Email. The matrix shows each type's current choice.

Locked rows show a padlock and an Always on tag, and always deliver in both channels. They include invites, security notices, export readiness, deletion scheduling, payment failures and cancellation receipts.

Changes take effect immediately; there is no save button.

What language and timezone are my emails in?

Emails are written in your language and show dates in your timezone - not the language of whoever triggered them. This follows the Language, Timezone and Date format settings you pick under Settings → Appearance → Region & Language:

• If you chose a specific Language (English or German), your emails use it.
• If you left Language on Automatic, emails follow the language your browser last used on Lumio. If you have never opened Lumio in a browser, they default to English.
• Dates and times in an email use your Timezone choice first, then the last timezone your browser reported, then UTC. Numeric dates follow your Date format; written weekday and month names follow your language. The stream summary's heading uses your time format for its time range.

You do not set this separately for email; it reuses your display preferences. For emails that go to a channel's owner (the stream summary and the reconnect required alert), it is the owner's language and timezone that apply.

Actions

Actionable notifications have one or more buttons below the message. View, Review and similar buttons open a page. Invite buttons act in the bell:

• 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.
• Accept a developer-team invite - joins the team and opens its dashboard page.
• Decline a developer-team invite - removes an unused single-use invite. A shared or already-used invite stays available for others. If the invite has already gone, the bell simply clears the action.

Clicking an invite action disables both buttons while the server processes the request. If it fails (e.g. the invite expired or you are already a member), an error message appears at the bottom right and the buttons re-enable. You can retry or open the invitation link.

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.

Retention

Read notifications are deleted automatically 90 days after they arrived. Unread notifications stay until you read or delete them.

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)
Open the bell to mark all as read	(none - your own)
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. Declining an account invite removes it. Declining a developer-team invite removes it only when it is unused and single-use; a shared link can still be used by others.
• 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.
• Open the bell to review new notices. Opening clears the unread badge; notifications remain in the list until you delete them or they expire.

Troubleshooting

Badge shows a number but the dropdown contains no unread items. The dropdown shows the 10 most recent notifications regardless of read state, while the badge counts every unread one. Older unread items may be outside the visible ten; opening the bell marks those as read too and clears the badge.

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 Settings → Notifications and set configurable types to Off, In-App (no email), or Email (no bell entry). Locked notices 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.