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
| Layer | Configured how | Applies to |
|---|---|---|
| Server owner | Automatic (no config) | Everything — owner can never be moderated by any bot (Discord platform rule) |
| Administrator perm | Automatic | Chat-content rules (URL gate, banned phrases, etc.). Does NOT exempt from anti-nuke by design. |
| Exempt users | Textarea of user IDs in the dashboard | All Zippy Wall layers including anti-nuke |
| Exempt roles | Textarea of role IDs in the dashboard | All Zippy Wall layers including anti-nuke |
| Ignored channels | Per-channel ID list in the dashboard | All messages in that channel — useful for "anything goes" chats |
Setting it up
For each user or role you want to exempt:
- Enable Developer Mode in Discord: User Settings → Advanced → Developer Mode
- Right-click the user/role → Copy User ID (or Copy Role ID)
- Paste into the corresponding textarea in your guild's Zippy Wall dashboard (one ID per line)
- Save settings
Why Administrator doesn't auto-exempt anti-nuke
Anti-nuke'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.