Alerts
Key features
Configurable audit alerts
Enable individual alert types, choose the destination channel for each one, and set the embed colour used when Nox posts the alert.
Native Discord event coverage
Route alerts for joins, leaves, bans, unbans, kicks, role changes, channel changes, role deletion, and voice join or leave events.
Feature alerts
Tickets, Warnings, and Temporary Voice can emit operational alerts to the same alert system so staff see feature events in the channels they already watch.
Queued delivery with error reporting
Most alerts re-check the saved configuration before sending. Delivery failures are recorded on the Errors page so admins can repair channels or permissions.
Best for
Staff audit channels for member, role, channel, voice, ticket, warning, and temporary voice activity.
Communities that want Discord-side events visible without manually checking Discord audit logs.
Separating alerts by audience, such as moderation events in one channel and support feature events in another.
How it works
Admins configure alert keys
In the Alerts modal, admins enable each alert key, choose a target channel, and select the colour used for alert embeds.
Nox sees an event or feature action
Discord events, audit-log events, ticket actions, temp voice actions, and warning actions can send matching alerts.
The alert is sent if still enabled
Alerts read the latest saved alert channel before sending, so old pending work does not post after an alert is disabled or moved.
Failures are shown in Errors
If delivery fails, Nox records the feature and failure context on the Errors page so admins can repair channels or permissions.
Setup checklist
Create staff channels for the alert categories your team will actually monitor.
Enable only the alert keys that should post and choose a channel for every enabled key.
Confirm Nox can view, send, and embed in each alert channel.
Grant View Audit Log when you expect kick or audit-log-derived alerts.
Use distinct colours when several alert types post into the same channel.
Important notes
Alerts are not the same as Activity Log. Alerts post Discord messages; Activity Log stores product activity and error records inside the dashboard.
Most alerts are sent by background delivery, but Warnings still send their warning-specific audit alerts directly from the bot.
Member leave, kick, ban, and unban alerts come from different Discord event sources, so enabling one does not imply the others are enabled.
Alert messages are not tracked after delivery. Deleting an alert message in Discord does not remove dashboard history or feature state.
There are no Alerts slash commands; configuration happens in the web app.
Troubleshooting
An alert did not post
Check that the specific alert key is enabled, has a channel, and that Nox can view, send, and embed in that channel. Also check unresolved Alerts errors.
Kick or audit-log alerts are missing
Confirm Nox has View Audit Log and that the relevant key is enabled. Leave, kick, ban, and unban alerts are separate settings.
An old alert posted after a settings change
Delivery re-checks the saved alert config before sending. If an old alert appears, verify the saved channel/key in Alerts and check whether the event came from Warnings.
Permissions
Discord permissions Nox needs for this feature and what each permission is used for.
