Docs

Permissions

Warden has two separate permission layers. Mixing them up is the most common source of confusion.

Server permissions

Granted by LuckPerms or any permission plugin. They decide who may type a command at all.

NodeDefaultCovers
warden.command.<subcommand>trueOne subcommand each: help, menu, info, list, create, disband, leave, invite, accept, decline, join, requests, kick, setrole, transfer, home, sethome, description, tagcolor, access, deposit, withdraw, banklog, war, chat, stats, relation, top, upgrade
warden.adminopThe entire /clan admin tree and the admin GUI
warden.upgrade.<category>trueBuying upgrades of one category: core, economic, progression, combat
warden.bank.currency.<currency>trueHandling one PulsePrison currency in the clan bank
warden.war.customprofileopChoosing a custom AtomCombat profile when declaring war

The node never changes when you rename a command. /gang guerra still checks warden.command.war.

Revoking warden.upgrade.economic from the default group and granting it to a donor rank is the intended way to sell upgrade categories as a perk.

Internal clan permissions

Defined in roles.yml, per role. They decide what a member may do inside their own clan, and no permission plugin is involved.

NodeAllows
clan.disbandDissolving the clan
clan.inviteInviting players
clan.kickKicking members
clan.setroleChanging roles
clan.transferTransferring leadership
clan.sethomeSetting the clan home
clan.warDeclaring, accepting and declining wars
clan.settingsDescription, tag colour and open/closed access
clan.requestsAccepting and denying join requests
clan.relationsAlliances and rivalries
clan.upgradesBuying upgrades
clan.bank.depositDepositing
clan.bank.withdrawWithdrawing

Both layers are checked. A player needs warden.command.kick from the server and clan.kick on their clan role.

Role rank also matters on its own: nobody can kick, promote or demote a member whose rank is equal or higher than theirs.

Permissions | Warden Docs