Permissions

Zira needs the following permissions on your server to operate properly. The invite link grants all of these by default.

Required Permissions#

Permission	How it is used
Manage Roles	To add and remove every Zira-managed role and create color roles
View Channels	To find target messages and see channels used by configured features
Send Messages	To send command responses, logs, giveaways, polls, suggestions, and setup messages
Send Messages in Threads	To reply or post when a configured destination is a thread
Manage Messages	To remove consumed reactions and clear reactions during migration
Embed Links	To send rich responses and messages from the Embed Builder
Read Message History	To fetch, edit, and attach features to existing messages
Add Reactions	To add reaction-role emoji
Use External Emojis	To use custom emoji from another server
Manage Channels	To create and delete Private Rooms
Move Members	To move members into their Private Rooms
Connect	To join the Private Rooms trigger while moving a member
Create Invite	To verify the invite requirement for servers enrolled in the Partner Program

The official invite asks for the full set above so every feature can work without a second permission pass. It never asks for Administrator.

Role position is separate from permissions. Even with Manage Roles, Zira can only add or remove roles placed below Zira's highest role. Managed roles, such as bot, integration, and Server Booster roles, cannot be assigned by another bot.

Channel overrides also matter. A green permission on Zira's server role can still be denied in one channel. When a feature works elsewhere but not in one channel, check Edit Channel → Permissions → Zira in that channel and its parent category.

Command Permissions#

By default, Zira's management commands need the Manage Server permission (/temprole needs Manage Roles). Zira checks this itself when the command runs, so members without the permission see a private "missing permission" message that tells them exactly what to ask an admin for.

You can still use Server Settings → Integrations → Zira to restrict where commands can be used, for example hiding them in certain channels or from certain roles. To grant command access to members who don't have Manage Server, use the roles below instead: Zira checks its own permissions, so an Integrations override on its own won't unlock a command.

Command Role#

The command role gives its members access to every Zira command and the dashboard, even if they don't have the Manage Server permission:

/config role set <Role>

Setting a command role also locks Zira down: while one is set, members who are not in the role cannot use commands at all, even with Manage Server. Only the server owner and members with Administrator always keep access.

To clear the command role and return to the normal Manage Server requirement:

/config role disable

Giveaway Manager Role#

If someone should run giveaways but nothing else, use the giveaway manager role instead:

/config giveaway-manager set <Role>

Members of that role can use /giveaway and sign in to the dashboard, where they see just the Giveaways page: they can create, edit, draw, reroll, and cancel giveaways, but they cannot delete giveaway history or change giveaway settings (including the manager role itself). You can also set it on the dashboard under Giveaways → Giveaway settings, and clear it with /config giveaway-manager disable.

Dashboard Access#

The dashboard follows the same access rules as commands:

• The server owner and Administrators always have access.
• Without a command role, members with Manage Server have access.
• With a command role set, its members have access and ordinary Manage Server members are locked out.
• The giveaway manager role gets access only to giveaway operations.

If a server does not appear after you sign in, confirm that you are still a member, that Zira is still in it, and that your Discord role grants one of the access paths above. Then sign out and back in so Discord can refresh your server list.