Permissions

Bot permissions

When you invite Iridex, it requests these Discord permissions:

Iridex's highest role must be above any role it needs to manage, a Discord-wide rule for all bots, not specific to Iridex.

Command permissions

Each command lists a required Discord permission on its commands page. Discord hides commands from members who don't have that permission automatically. Commands marked None are usable by everyone.

Dashboard access

You can manage a server on the Iridex dashboard if:

Why each permission is needed

Iridex asks only for what its features use. If you do not use a feature, you can remove its permission and the rest keeps working. For example, a server that never uses tickets can leave out Manage Channels, and one without moderation can leave out Kick, Ban and Moderate Members.

Channel-level permissions

Server-wide permissions are only half of the story. A channel's own settings can override them, so if Iridex cannot post somewhere, open that channel's permissions and check that the Iridex role (or the bot) is allowed to View Channel, Send Messages and Embed Links. Private staff channels need the bot added explicitly.

The role hierarchy

Discord orders roles from top to bottom. A bot can only add, remove or act on members and roles below its own highest role. Put Iridex above the roles it manages and below your staff roles. This is a Discord rule that applies to every bot.

What Iridex does not ask for

Iridex does not need Administrator. It does not read your direct messages and it only reads message content where a feature, such as the word filter or anti-scam, needs it to do its job.

Giving staff access without Administrator

Use the Staff Access tab or /dashboardaccess to let specific people edit Iridex's settings. This is separate from Discord permissions: they can change how Iridex behaves, but they cannot change your server's roles or channels.

Revoking access

Remove someone from Staff Access at any time and they lose dashboard access immediately. Removing Administrator from a member does the same for them, since dashboard access follows their permissions.