Wicks permissions and role order
If Wicks can see a channel but cannot run an action or assign a role, the cause is usually a missing channel permission or role order.
The most important rule
Open Server Settings → Roles and move the Wicks role above every role it needs to assign or remove, and above members it may need to moderate.
Wicks cannot manage a member or role above its own role—even with Administrator—and it cannot manage the server owner.
Permissions by task
| Task | Core permissions |
|---|---|
| Messages and images | View Channels, Send Messages, Embed Links, Attach Files |
| Tickets | Manage Channels, Manage Roles |
| Color, level, and welcome roles | Manage Roles |
| Logs and protection | View Audit Log |
| Message cleanup | Manage Messages |
| Ban, kick, and timeout | Ban Members, Kick Members, Moderate Members |
| Voice moderation | Move Members, Mute Members |
Check channel permissions too
A channel or category can deny a permission that the server role allows. Open Edit Channel → Permissions and make sure Wicks has no red deny for the action it needs.
Send an Embed in a private test channel, then create a test role below Wicks and assign it to a test member. This verifies messaging and role order.
Should I use Administrator?
Administrator makes the first setup easier but grants broad access. You can instead give Wicks the permissions above as you enable each module.