Permissions: who can do what?

Three layers work together in yurna: access to the dashboard, permissions for individual slash commands and the permissions of the bot itself. All three are based on your roles' Discord permissions – yurna doesn't need its own user management.

In the dashboard#

Under Dashboard → Server & plan → Settings → Roles & permissions (/dashboard/<server>/settings/rollen) you see every role of your server at a glance:

1. Pick the view at the top: Overview shows all roles as a table (members, admin, dashboard, commands, risky permissions, teams, exceptions, assigned by). Per role shows the details.
2. Search for a role by name or ID and open it.
3. Discord permissions shows what the role may do on the server. With Show missing permissions too you see every permission, the missing ones struck through.
4. yurna commands shows which commands a member with exactly this role can use – with the reason, such as "Blocked for this role in Discord".
5. Dashboard & modules shows whether the role can open the dashboard and in which modules it's used (e.g. ticket team or verification role).

The page is view only – you don't change anything here. You change permissions in Discord and switch commands on or off under Modules & commands → Commands. A short version is also available in Discord: /server roles (see By command).

Who can use the dashboard?#

Anyone with Manage Server or Administrator on a server can open its dashboard; the server owner has both anyway. Server & plan → Settings → Dashboard Access shows which roles that applies to on your server.

To give someone access, grant their role one of these permissions in Discord. If the server still doesn't show up in their server list, they can click Reload list there.

Who can use which commands?#

Most commands are open to all members. Commands for team tasks come with a default permission: members without it don't even see the command in Discord.

Switching commands on and off#

Under Modules & commands → Commands (/dashboard/<server>/modules?reiter=befehle) you control what runs on your server at all:

1. Switch off a whole category at the top, for example “Fun” if you don't want fun commands.
2. Expand a category below and switch off individual commands. This only works while the category itself is on.

You can do the same in Discord with /server module enable or /server module disable (option command or category). Bundled commands such as /fun or /game are still listed part by part under their old names, e.g. "8ball" – see New command names.

A disabled command stays visible in Discord. Anyone who uses it gets a “Command disabled” or “Command category disabled” notice; members with Manage Server or Administrator are also told they can turn it back on in the dashboard.

The bot's own permissions#

What yurna itself is allowed to do depends on its role's permissions. Use /yurna permissions to check that everything is in place. If yurna should assign roles, its role has to sit above those roles in the role list.

By command#

/server roles is view only and needs "Manage Server"; only you see the reply. The matrix in the dashboard shows exactly which commands a role can use – the Open in dashboard button takes you there.

Common questions#

Why can't a member see a command?#

The command needs a permission their roles don't have, or it's blocked in Discord under Integrations → yurna. Roles & permissions shows you the reason per role.

Can I give someone only the dashboard, without "Manage Server"?#

No. Only people with "Manage Server" or "Administrator" can open the dashboard.

Why doesn't yurna assign a role?#

yurna's role has to sit above that role in the role list. Roles & permissions marks roles that are too high.

What does missing "Use Application Commands" mean?#

Members with only this role can't use any slash commands. Give the role (or @everyone) that permission in Discord.

See also#

• Inviting yurna
• Command overview
• Server settings
• Permission problems
• Commands missing in Discord