Surfaces
Notification Config
Discord webhook routing for operational event notifications.
First created Last updated
Overview
Notification Config sends selected event activity to a private Discord webhook. It is meant for operator awareness, not attendee announcements.
The webhook should point to a staff-only channel because events can include registration, refund, upgrade, submission, and account-capacity signals that are not appropriate for public channels.
Dashboard route
/ems/manage/notification-config?id=:eventId
Inputs and controls
| Input or option | What it changes | Before saving |
|---|---|---|
| Enable notifications | Turns webhook delivery on or off for the event. | Confirm the webhook channel is private and monitored. |
| Discord webhook URL | Destination for event notifications. | Treat as a secret; rotate it if exposed. |
| Event type checkboxes | Selects the specific alert categories posted to Discord. | If notifications are enabled, at least one event type must be selected. |
| What gets posted preview | Explains the kind of context Discord receives. | Confirm the staff channel is appropriate for that level of operational detail. |
| Floating save bar | Saves or reverts webhook and event type changes. | Revert if the webhook URL or selected categories were changed accidentally. |
Page states
| State | What it means | What to do |
|---|---|---|
| Notifications disabled | No event notifications are sent to the webhook from this config. | Keep disabled until the webhook is private, tested, and monitored. |
| Notifications enabled with no event types | The configuration is incomplete. | Select at least one event type before saving. |
| Webhook validation error | The URL is missing or not a supported Discord webhook URL. | Paste a webhook from Discord’s integration settings and keep it private. |
| Dirty save bar visible | The webhook URL, enabled switch, or event type selection changed. | Save after review or revert to discard the draft. |
Event type options
| Option | Posts when | Use when |
|---|---|---|
| Settings changes | Operators save event setup changes from the dashboard. | Setup changes need staff awareness or audit visibility. |
| New regos | An attendee submits a new event registration. | Registration volume should be watched in Discord. |
| New applications | A Dealers Den application is submitted. | Dealer review is time-sensitive. |
| Volunteer applications | An attendee applies for a volunteer position. | HR leads review applications from Discord alerts. |
| Activity submissions | An attendee submits an activity form entry for review. | Programming or conbook teams need queue awareness. |
| Waitlist joins | An attendee joins a tier waitlist. | Capacity is tight or being actively monitored. |
| Waitlist offers | The next attendee in queue is offered an available registration spot. | Staff need to know when queue movement starts. |
| Declined waitlist offers | An attendee declines a waitlist offer and the queue advances. | Staff need to track churn or follow-up. |
| Refund requests | An attendee submits a refund request. | Finance review should happen quickly. |
| Approved refunds | An operator approves a refund request. | Finance handoff needs visibility. |
| Declined refunds | An operator declines a refund request. | Support teams may receive follow-up questions. |
| Registration refunded | A registration is marked refunded and a slot is freed. | Capacity or waitlist movement may be affected. |
| Upgrade requests | An attendee submits an upgrade request. | Upgrade review is part of daily operations. |
| Accepted upgrades | An operator accepts an upgrade request pending payment. | Staff should monitor payment/finalization. |
| Declined upgrades | An operator declines an upgrade request. | Support may need context. |
| Finalized upgrades | An upgrade is fully applied to the attendee registration. | Entitlements, capacity, or fulfillment may change. |
| Transfer requests | An attendee requests to transfer their registration. | Identity-sensitive ownership changes need review. |
| Approved transfers | An operator approves a registration transfer. | Staff should know access moved to another attendee. |
| Declined transfers | An operator declines a registration transfer. | Support may receive questions. |
| Payment account full | Attendee reports auto-flag a payment account as full or needing review. | Finance staff should check account capacity. |
| Payment account auto rollover | The system points attendees to the next available payment account. | Finance staff should confirm the new receiving account is ready. |
Validation rules
If notifications are enabled, the webhook URL must be a Discord webhook under discord.com, discordapp.com, canary.discord.com, or ptb.discord.com with an /api/webhooks/ path. The config must also include at least one selected event type.
Flowchart context
Notification Config supports Active Event Workflow by making queues visible to staff. Link it with Communications only for operational awareness; attendee-facing email blasts are handled separately.
Common mistakes
Do not route notifications to a social or public Discord channel. Webhook traffic should be limited to operators who are allowed to see event operational records.