- Documentation
- FAQ
- yurna is missing permissions
yurna is missing permissions
When yurna does nothing, won't assign a role or an action fails: check permissions, channel overrides and the role hierarchy.
When yurna "does nothing", doesn't hand out a role or a moderation action fails, it's almost always about permissions. Discord checks three things: the server permissions of yurna's role, channel overrides, and the role hierarchy.
How to check#
- Type
/permissionson the server. yurna lists every permission it needs with a tick or a cross. If something is missing, give yurna's role that permission under Server Settings → Roles. - Check the affected channel: Edit Channel → Permissions. An override for @everyone or another role can take permissions away from yurna there, even if it has them server-wide.
- Check the order under Server Settings → Roles: yurna's role has to be above every role yurna should add or remove, and above the members it should moderate.
Note
/permissions only checks server-wide permissions. Whether a single channel blocks yurna is only visible in that channel's permissions.
Which permissions yurna needs#
The invite link asks for exactly these permissions – Administrator isn't required.
| Permission | What it's for |
|---|---|
| View Channels, Send Messages, Send Messages in Threads | Replies, logs and every message yurna sends |
| Embed Links | Almost all replies are embeds |
| Attach Files | Image commands, welcome image, cards |
| Add Reactions, Use External Emojis | /poll, reaction roles, emojis in messages |
| Read Message History | Ticket transcripts, verification messages, /clear |
| Manage Messages | /clear and message deletion by Automod and Shield |
| Manage Roles | Adding and removing roles, ticket pings to roles that aren't mentionable |
| Manage Channels | Ticket channels, Join-to-Create, /slowmode |
| Manage Server, Manage Expressions | Server settings such as AutoMod rules and invites; /emoji |
| Manage Webhooks | Relaying in ticket and DM support |
| Kick Members, Ban Members, Timeout Members (Moderate Members) | Moderation, /timeout, Automod timeouts |
| Connect, Move Members | Join-to-Create |
| Mention @everyone, @here and All Roles | Pinging roles that aren't mentionable |
| Create Invite, Change Nickname, Manage Nicknames | Other features such as nicknames via /member |
Role hierarchy#
Discord only lets a bot manage roles below its highest role, and only moderate members whose highest role is lower than its own. No bot can moderate the server owner. On top of that, yurna can never assign @everyone or managed roles – roles that belong to bots, integrations or server boosters.
Typical messages are "Ban failed (permissions/role hierarchy?)", "The timeout couldn't be set (permissions/role hierarchy?)" or "I'm not allowed to give this role".
How to fix it:
- Open Server Settings → Roles.
- Drag yurna's role above the roles yurna should assign.
- Check whether the target role is a managed role (it's linked to an integration in Discord). yurna can't assign those.
Channel overrides#
When a channel denies yurna a permission, features there often fail without a loud error. Examples:
- Welcome messages: If "View Channels", "Send Messages", "Embed Links" or "Attach Files" is missing in the welcome channel, yurna sends nothing at all.
- Announcements: The dashboard reports that yurna is missing permissions in the channel (view channel, send messages, embed links).
- Tickets: yurna creates ticket channels with their own permissions. For that it needs "Manage Channels", and it must itself have server-wide the permissions it grants in the ticket channel (including View Channels, Send Messages, Read Message History, Embed Links and Attach Files).
Administrator – yes or no?#
/invite shows a recommended link with exactly the permissions needed and a second link with Administrator. We recommend the first one. If yurna is missing permissions later, give them to yurna's role by hand or re-authorise yurna through the invite link.
See also#
Last updated on 15 October 2026