Skip to Content
DocsDashboardSettingsNotification Settings

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.

Admin only

Notification Settings requires admin privileges (admin.settings.read). Navigate to Settings > Notifications from the sidebar.


Overview

✍️ Compose Notifications

Create and send push notifications to individual users or broadcast to all users

📜 Delivery History

View a complete history of sent notifications with recipient details and timestamps

📄 Templates

Save and manage reusable notification templates for common messages

📡 Channels

Configure how notifications are delivered — in-app, Discord webhooks, Discord bot, and Signal


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:

🔔

Built-In

In-App Notifications
💬

Messaging Integrations

Discord WebhooksDiscord BotSignal

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 webhooks

Send notifications to a Discord channel via webhook:

  • Enter your Discord webhook URL
  • Send a test notification to verify the integration
  • Notifications appear as rich embeds in your Discord channel

Discord bot

For more advanced Discord integration, configure a Discord bot:

  • Enter your bot token
  • Enable bot-based delivery for direct messages to users
  • Users need to link their Discord account to receive DMs

Signal

Send notifications via Signal messenger:

  • Requires signal-cli to be installed on the server
  • Register a phone number for Signal delivery
  • Configure the admin notification recipient

Email channel

Notifications can also be delivered via email when an email provider is configured in Email Settings. Users control their email notification preferences from their Profile page.


User notification preferences

While Notification Settings controls the system-wide channel configuration, individual users manage their own preferences from their Profile page. Users can choose which notification types they want to receive and through which channels, allowing them to opt out of non-critical notifications while still receiving security alerts.


Best practices

Do

  • Create templates for recurring notifications like maintenance windows or update announcements
  • Use the appropriate notification type (system, security, general) so users can filter notifications effectively
  • Send a test notification through each channel after setup to verify delivery
  • Use Discord webhooks for team-wide notifications — they are the easiest integration to configure
  • Include action links in notifications when there is a relevant page for the user to visit

Don't

  • Don't broadcast notifications for minor announcements — overuse leads users to ignore them
  • Don't configure the Discord bot without ensuring your bot has the required permissions in your Discord server
  • Don't forget to configure the email provider if you want email notifications — the notification system cannot send emails without it

FAQ

Users receive notifications through channels that are (1) configured by the admin in this page and (2) enabled in the user's own notification preferences. If a user has opted out of email notifications, they will not receive email delivery even if the email channel is configured.
Webhooks send notifications to a Discord channel — all members of that channel see the notification. The Discord bot can send direct messages to individual users based on their linked Discord account. Webhooks are simpler to set up; the bot provides more targeted delivery.
Signal integration uses signal-cli installed on your server. After installing signal-cli, you register a phone number, verify it, and then the dashboard can send messages through Signal. This requires a dedicated phone number for your server.
In-app notifications track read and dismissed status. You can see this in the History tab. External channel delivery (Discord, Signal, email) is fire-and-forget — the dashboard confirms the message was sent but does not track whether it was read in the external service.
The notification system includes retention cleanup that automatically removes old notifications. Notifications are also deleted when a user account is deleted.

Join the Community

Media server operators sharing configs, getting support, and shaping the future of QuickBox Pro.

Dedicated Support
Feature Previews
Community Configs
Active Discussions
Join Discord Server