Notification Settings

The Notification Settings page lets administrators compose and send notifications to users, manage notification templates, review delivery history, and configure notification channels. It is organized into four tabs: Compose, History, Templates, and Channels.

Overview

Compose tab

Create and send notifications from the Compose tab:

• Recipient selection — Send to a specific user or broadcast to all users
• Notification type — Categorize the notification (system, security, general, app, support)
• Title and body — Write the notification content with rich text formatting
• Action link — Optionally include a button that links to a specific page or URL

When you send a notification, it is delivered through all configured channels (in-app, Discord, Signal, email) based on each recipient’s notification preferences.

History tab

The History tab shows a complete record of all notifications sent through the system:

• View the sender, recipients, title, and timestamp of each notification
• Filter and search through notification history
• Track whether notifications were delivered successfully

This is useful for auditing what messages have been sent and when, especially for system-wide announcements or security alerts.

Templates tab

Save frequently used notification messages as templates:

• Create templates with pre-filled title, body, and type
• Edit or delete existing templates
• Load a template when composing a new notification to save time

Templates are useful for recurring messages like scheduled maintenance notices, welcome announcements, or security advisories.

Channels tab

Configure how notifications reach your users beyond the in-app notification center:

In-app notifications

In-app notifications are always available. Users see them in the Notification Center on their Profile page. A notification badge in the top bar shows the unread count.

Discord has two delivery methods, and the difference matters:

Discord bot (recommended)

Your install runs one Discord bot. With its token configured, the bot DMs alerts to each linked user and powers inbound commands — the same single token does both. To set it up:

• Create a Discord application with a bot and enable its Message Content intent
• Paste the bot token here and use Test Token to verify it
• Enable bot DM delivery, and optionally add your server’s invite link so users can join
• Each user enters their Discord User ID (and links their account) to opt in to bot DMs

The full step-by-step bot setup, including how to get the bot somewhere it can DM your users, lives on the QBxBot Command Channel page — the same bot is used for both alerts and commands.

Discord webhooks (optional)

A webhook is an optional, outbound-only extra — it posts notifications into a Discord channel but cannot receive commands. Each user manages their own webhooks from their Profile notification settings, and can go well beyond a single URL:

• Name multiple webhooks — add up to 10 webhooks, each with a name you choose (for example, “General Logs”, “Critical Alerts”, or “Downloads”). One is marked the default, and each has its own Test button.
• Route events per webhook — for any notification event, pick which named webhook it posts to, or leave it on Default. The per-event webhook picker appears once a user has two or more webhooks.
• Send events silently — each event can post silently (logged to the channel with no push notification, using Discord’s suppress-notifications flag) or notify as usual. It is a per-event choice of Default (inherit the channel’s Default silent delivery setting), Silent, or Notify — so routine events stay quiet while important alerts still ping.

Notifications appear as rich embeds in your Discord channel. A user can use the bot DM, one or more named webhooks, or both. By default, once their account is linked, alerts arrive as a bot DM; a webhook adds a channel copy. Existing users who set up a single webhook are unaffected — it becomes their default automatically.

Signal

Send notifications via Signal messenger. Signal works in two layers:

1. Install-wide (administrator). An administrator gives this install a Signal identity for QBxBot to send from. The easiest way is Link Device — QBxBot shows a QR code that you scan from Signal → Settings → Linked Devices on your phone, attaching it as a second device without needing a spare number. Alternatively, Register Number claims a dedicated phone number outright. The Channels tab also has an Install button that prepares signal-cli (and its Java runtime) for you. Once the identity is set, enable Signal.
2. Per-user. Each user who wants Signal alerts sets their own Signal recipient number and turns on the Signal channel for the events they care about, from their Profile notification settings.

WhatsApp

WhatsApp delivery is coming soon. It appears in the channel list as a placeholder; once available, users will be able to receive alerts at a verified WhatsApp number through a provider integration.

User notification preferences

While the Channels tab controls the install-wide configuration, each user manages their own preferences from the notification settings on their Profile page. There a user picks which channels they want overall, then fine-tunes individual events — opting out of non-critical alerts while still receiving security ones.

Channels and per-event overrides

A user first chooses their global channels — in-app, email, realtime, Discord, Signal, and (coming soon) WhatsApp. Those global choices apply to every event unless the user overrides a specific event. Each event row offers per-channel toggles, so someone can, for example, get security alerts by email but app-status alerts only in-app.

Event groups

Events are organized into groups so users can tune them at a glance:

Disk-usage thresholds

In the Applications & Services group, the disk-usage alert lets a user pick the fill levels they want to be warned at — presets of 80%, 90%, and 95%, plus a few custom thresholds of their own between 1% and 99%. They are notified each time usage crosses a level they enabled.

Updates digest

Instead of a separate alert for every available update, a user can switch on the updates digest — a single roll-up sent daily or weekly at a chosen day, hour, and timezone. When the digest is on, the individual update-available alerts are replaced by the scheduled summary.

Quiet hours

Quiet hours mute non-critical alerts between the hours a user sets, so overnight or focus-time notifications hold until later without missing anything important.

Best practices

FAQ

Related pages