Who can run a command
By default each command needs one Discord permission, listed on All commands./giveaway start needs Manage Server, /sticky set needs Manage Messages, and fun commands need nothing.
The server owner and anyone with Administrator can always run everything. Two exceptions: a moderator the anti-nuke stopped can’t moderate until resumed, and /antinuke is for the owner and trusted admins only.
Give your mods access
Moderation commands follow the Moderation tab only: a role’s switches, plus the ones its Discord permissions lock on. A member with Ban Members can use
/ban, and the anti-nuke counts their bans either way.1
Open the Moderation tab
On the dashboard, pick your server and open Moderation.
2
Add your mod roles
Roles that can already moderate in Discord list themselves, with a padlock on what Discord gives them. Open a role to switch on more, or add another at the bottom: ban, kick, timeout, voice mute, voice deafen, warn, restrict, purge, lockdown and cases.
3
Save
Click Save in the bar at the bottom. Your mods can now use what you switched on.
Switch a command off
Open the Commands tab and switch a command or a whole category off. Off means off for everyone, the owner included. Anyone who tries it is told an admin switched it off. This is all most servers need.Advanced Permissions
The Advanced Permissions tab sets rules for exactly who can run each command. Moderation isn’t set here: use the Moderation tab.1
Switch it on
Tick Use Advanced Permissions. It’s off by default, and while it’s off nothing on the tab counts.
2
Pick what to change
Open a category, like Giveaways, or add one command under Single commands.
3
Set each role
Set roles to Default, Allow or Block, then click Save permissions.
Default
Default
Nothing changes for the role. Its members use the command with their normal Discord permission. Once any role is set to Allow, roles left on Default can’t use it.
Allow
Allow
The role can use the command, even without the Discord permission it normally needs. Once one role is allowed, only allowed roles can.
Block
Block
The role can’t use the command, even if another of its roles is allowed. Block always wins.
Whitelist
Whitelist
Whitelisted roles can use every command, moderation included, and no rule can block them. Only the owner and trusted admins can change it.
Categories and single commands
Categories and single commands
A category rule covers every command in it. A rule for one command replaces the category rule for that command.
Channels and single people
Channels and single people
Under More, keep a rule to certain channels, or allow or block single people by user ID.
What Newt needs
Newt never needs Administrator. Each permission below is only for the features next to it. When Newt is missing one, the command names it, and the dashboard says so on the tab it’s for.Permissions audit
The Permissions audit tab reads every role and channel override and flags risky permissions, like Administrator or Manage Webhooks on a role that doesn’t need them. Each warning says how to fix it. If one is on purpose, click Ignore this warning.Good to know
- The owner and Administrators are never blocked by an Advanced Permissions rule.
- Block a role and everyone else keeps the command’s normal Discord permission.
- The Whitelist only counts while Advanced Permissions is on.
- While a Whitelist is set, only the owner and trusted admins can switch Advanced Permissions on.
- Moderation rules saved on the old Permissions tab no longer count. Set mods up on the Moderation tab.
- Nobody but the server owner can set Newt up to hand out a role at or above their own highest role, the same rule Discord has for giving roles by hand.
- Pings and punishments follow your own permissions. Picking a role that can’t be mentioned, for Newt to ping, needs Mention Everyone. Setting automod, the join gate or warnings to time out, kick, ban or restrict needs that same permission on your own account.
