Whitelist

Five layers of exemption let you bypass Zippy Wall for trusted users. They're evaluated in order — the first match wins.

The five exemption layers

LayerConfigured howApplies to
Server ownerAutomatic (no config)Everything — owner can never be moderated by any bot (Discord platform rule)
Administrator permAutomaticChat-content rules (URL gate, banned phrases, etc.). Does NOT exempt from AntiNuke by design.
Exempt usersTextarea of user IDs in the dashboardAll Zippy Wall layers including AntiNuke
Exempt rolesTextarea of role IDs in the dashboardAll Zippy Wall layers including AntiNuke
Ignored channelsPer-channel ID list in the dashboardAll messages in that channel — useful for "anything goes" chats

Setting it up

For each user or role you want to exempt:

  1. Enable Developer Mode in Discord: User Settings → Advanced → Developer Mode
  2. Right-click the user/role → Copy User ID (or Copy Role ID)
  3. Paste into the corresponding textarea in your guild's Zippy Wall dashboard (one ID per line)
  4. Save settings

Why Administrator doesn't auto-exempt AntiNuke

AntiNuke's entire purpose is to catch compromised admin accounts. If users with the Administrator permission were auto-exempt, the feature would do nothing — that's exactly the attacker we're trying to stop.

For legitimate admins who do high-volume cleanup work (post-raid bans, mass-channel-rearrangements), add them to Exempt users or give them a role in Exempt roles. That explicitly says "I trust this person's account" — which is a stronger signal than "this account has Administrator permission."

Twitch-side whitelist

Twitch has its own Exempt users textarea (Twitch user IDs, not logins — IDs don't change when someone renames). Broadcaster and moderators are auto-exempt regardless of the textarea contents.

Configure in your dashboard.