Moderation and safety

Set up server protection

Wicks Protection limits abuse of moderation permissions. You choose which roles to watch, how many actions they may perform, and what happens when they cross the limit.

Protection settings are owner-only

Only the server owner can open this page, even when another member has Administrator.

PathDashboard → Your server → Protection

Add a moderation role

Choose a role under Moderation Roles, then configure Ban, Kick, Role Update, and Channel Update separately. For each one, set an Action Limit and a response: None, Remove Roles, Kick, Ban, Warn, or Notification. A limit of 0 means unlimited.

1. Add one moderation role.
2. Start with a limit that allows normal staff work.
3. Use Notification or Warn for the first test.
4. Save, then repeat for other staff roles when needed.

Do not start with Ban

Test on a separate server or with a reviewable response. A very low limit can mistake trusted staff work for an attack.

Dashboard access

• Restrict to Owner: overrides everything and allows only the owner.
• Administrator: allows members with Administrator.
• Manage Server: allows a broader management team.

Trusted bots

Add only trusted administrative bot IDs so their actions do not trigger protection. Enable Discord Developer Mode, right-click the bot, and choose Copy User ID.

Safe test

Use a test role and a low limit with Notification, perform a monitored action, and confirm Wicks records it without applying a punishment.

If nothing happens, check View Audit Log, Wicks role order, the selected limit, and whether the test account is trusted.