Tutorials

Setting Up and Using Notifications

Create useful notification rules without spamming staff, mixing incompatible event families, or sending blank merge fields.

Moderation and Support

Who uses it: Managers and operations staff
Where it lives: Dashboard > Inbox > Rules
Goal: Guilds receive the right alerts in the right place, with useful context and safe delivery behavior.

On This Page5 sections

Before You Start

Notification manage permission.
At least one destination: channel, staff DM group, user DM topic, or Web Inbox.
A specific event you want to react to.

Steps

Choose the starting point
Start with the object family: Gear Checks, Review Queue, Evidence, Support Tickets, RaidHelper, Billing, or Operations. This choice controls which triggers, conditions, and merge fields are relevant.
Pick a destination
Use channels for shared staff visibility, staff DMs for urgent role-based alerts, Web Inbox for dashboard triage, and user opt-in DMs for member-specific updates.
Use compatible fields
Insert merge fields from the picker for the selected starting point. If the UI warns that a field may be blank or incompatible, change the field or the trigger.
Control noise
Set cooldown, dedupe, quiet hours, and scope before enabling. A good rule should be useful when it fires and quiet when nothing needs action.
Test and monitor
Send a test notification, then check delivery history and Web Inbox. If delivery fails, check destination health and permissions before editing the rule logic.
Know about the default rules
By the time you open Inbox > Rules for a guild, a set of default rules is already there, seeded automatically so you get useful alerts, like review queue activity, billing attention, and support tickets, without building anything yourself. Default rules can't be deleted, but they're yours to shape: edit one, or turn it off if you don't want it.