Permissions
How AntiRaid's permission system works and which nodes control each command.
How permissions work
AntiRaid uses a system called Kittycat to control who can run which commands. Rather than relying purely on Discord roles, you assign specific permission nodes to roles or individual users through the AntiRaid dashboard.
A permission node looks like backup.create or moderation.ban. Nodes follow a category.action pattern, and the wildcard category.* grants every action in that category at once.
AntiRaid checks both the Kittycat node and the required Discord permission before allowing a command. Having the Kittycat node alone is not enough if Discord's own permission check fails.
Utility commands are open to everyone
Commands like /whois, /remindme, /afk, and /server-info don't require
any Kittycat node — any member can use them.
Assigning permissions
Permission nodes reference
Backups
| Node | What it allows |
|---|---|
backup.view | List and view existing backups (/backups list) |
backup.create | Create and delete backups (/backups create, /backups delete) |
backup.restore | Restore a backup (/backups restore) |
backup.* | All backup commands |
Moderation
| Node | What it allows |
|---|---|
moderation.ban | Ban members (/moderation ban) |
moderation.kick | Kick members (/moderation kick) |
moderation.unban | Unban members (/moderation unban) |
moderation.* | All moderation commands |
Lockdown
| Node | What it allows |
|---|---|
lockdown.* | All lockdown commands (/lockdowns) |
URL Blocking
| Node | What it allows |
|---|---|
urlblock.add | Add a blocked URL |
urlblock.delete | Remove a blocked URL |
urlblock.enable | Enable URL blocking |
urlblock.disable | Disable URL blocking |
urlblock.list | View the blocked URL list |
Global
| Node | What it allows |
|---|---|
global.* | All commands across every category |