Skip to main content
Admin Access is the default permission level for most module commands. It allows server administrators to configure bot features without needing to be explicitly added to any permission list.

How Admin Access Works

Unlike Extra Owners and Trusted Users (which are explicit lists), Admin Access is determined automatically based on two conditions that must both be true:
1

Administrator Permission

The user must have the Administrator permission in Discord, either directly or through one of their roles.
2

Role Hierarchy

The user’s top role must be positioned higher than the bot’s top role in the server’s role list.
Both conditions are required. Having Administrator permission alone is not enough — your highest role must also be above the bot’s role in the hierarchy. This prevents lower-ranked admins from controlling a bot that outranks them.

Why Both Conditions?

This dual-check exists as a security measure. In large servers, multiple users may have the Administrator permission through various roles. The role hierarchy check ensures that only administrators who outrank the bot can configure it, preventing misuse by lower-level admins.
Example Role Hierarchy:
──────────────────────
  1. Server Owner
  2. Head Admin       ← Can use bot commands (above bot)
  3. ZEON Bot Role
  4. Junior Admin     ← Cannot use bot commands (below bot)
  5. Moderator
  6. @everyone
This check is completely bypassed for Server Owners, Extra Owners, and Trusted Users. They can use commands regardless of their role position.

What Admin Access Covers

Users with Admin Access can use any command gated by the top_check permission level, which includes:
  • Setting up and managing all module configurations (Greet, Boost Greet, Leave Message, etc.)
  • Using the Embed Builder commands
  • Running module test and show commands

What Admin Access Does Not Cover

  • Managing Extra Owners (requires Server Owner)
  • Managing Trusted Users (requires Server Owner / Extra Owner)
  • Configuring Antinuke settings (requires Server Owner / Extra Owner)
If you want a staff member to have bot access but they don’t meet the Admin check requirements (e.g., their role is below the bot), add them as a Trusted User instead using .trusted add @user.