The centre shows the latest available notifications from supported application and Qel Connect feeds. You can review unread items, mark an item read, and dismiss items. Older items may be loaded in pages. Realtime events can update the interface, while durable notifications are stored through the notification service.

If a notification feed is temporarily unavailable, the centre keeps previously loaded items visible, identifies the feed that needs refreshing, and retries automatically. Use Refresh to retry immediately.

In Settings → Notifications, users can mute supported event categories and choose whether to receive email notifications and the available cadence. Muting a category affects its notification delivery according to the saved preference. Qel Connect notification settings have their own controls where applicable.

Email delivery is optional and is available only when the deployment configures an SMTP host and sender, enables the required credentials, and runs the notification worker and scheduler. If email is unavailable, in-app notifications can still work. Email delivery may be retried; the system cannot guarantee exactly-once delivery from an external SMTP service.

Notifications do not fabricate payment or subscription lifecycle events: the current product does not have a paid-subscription source of truth. Provider alerts follow explicit health-test failures; this is not a continuous provider uptime monitor.

Notification content is designed to avoid including prompts, provider credentials, raw exception details, or internal support notes. Notifications are scoped to the account and tenant authorized for the underlying event. Support messages are readable by the submitter and assigned Support Managers. Feedback messages are readable by the submitter and assigned Feedback Managers; neither workflow is end-to-end encrypted.