Running a populated FiveM server without a proper staff hierarchy is a liability. One moderator with too many permissions or a junior admin who can’t do basic player management without calling the owner — both situations slow down a server’s operation. CodeM mStaff is built around solving that problem: a tiered permission system where every staff rank gets exactly the tools they need and nothing more.

Staff Hierarchy That Actually Works

mStaff implements a layered permission model with owner, admin, and sub-staff tiers. Owners assign which capabilities each rank can access, so a trial moderator can kick and warn players without ever seeing ban controls or financial commands. That separation keeps junior staff useful from day one without exposing server-critical tools to people who shouldn’t have them.

• Hierarchical permission system with owner, admin, and configurable sub-staff tiers
• Per-rank capability assignment — each role sees only the actions it’s authorized to perform
• Player management: teleport to/from, revive, heal, freeze, and spectate any connected player
• Vehicle controls: spawn, delete, repair, and modify vehicle properties on demand
• Moderation tools: bans, kicks, and warnings with reason logging and audit trail
• Server-wide actions: weather and time control, clear area, NPC management
• Noclip toggle and god mode for staff investigation and scene setup
• ESX and QBCore framework support with framework-aware permission enforcement

Practical Moderation for Active Servers

The design priority in mStaff is speed. Staff calls come in fast during peak hours, and a cluttered admin menu costs response time. The interface surfaces the most-used actions at the top tier, with deeper configuration and audit tools accessible without hunting through nested submenus. Documentation lives in CodeM’s GitBook, so onboarding new staff members to the system takes minutes rather than a training session.

Part of the CodeM Ecosystem

mStaff is included in CodeM’s premium subscription tiers and integrates cleanly with other CodeM resources running on the same server. If your server already runs CodeM’s MDT, HUD, or billing systems, adding mStaff won’t introduce conflicts — the resources share the same configuration conventions and framework hooks.