Introducing the New MonoAdmin

MonoAdmin is a cloud admin platform for FiveM servers: live players and a live map, moderation that keeps working when the cloud is unreachable, player actions with verified results, reports, a Player Monitor, character and vehicle editing, analytics and inbound webhooks.

This is the new MonoAdmin, rebuilt from scratch. Here is what it is, who it is for, what you get, and how to start.

What MonoAdmin Is

Three pieces work together:

• The panel. A web app your staff open in a browser to run the server.
• The cloud. It keeps your players, punishments, reports and logs, and talks to your game server.
• The resource. A normal FiveM resource you add to your server. It links the server to the cloud.

There is nothing to configure in files. Settings come from the panel and reach a connected server at once.

Who It Is For

MonoAdmin is for FiveM server owners and the staff teams who run their communities. One project is one FiveM server. You own it, invite staff by email, and give each person a role that decides what they can do.

Roles are made of fine-grained permissions. Nobody can hand out a permission they do not hold, and every staff action lands in a searchable audit log. Accounts can use two-factor sign-in.

Works With Your Framework

Pick the framework your server runs when you create the project:

• ESX, QBCore and Qbox get everything, including character, inventory and owned-vehicle data. Character and vehicle data need oxmysql. ESX 1.13.5 and later is supported.
• Standalone servers get moderation, the live map, the Player Monitor, reports and logs.

Inventory editing works with ox_inventory, and with qb-inventory on QBCore. Voice mutes work with the built-in Mumble voice and with pma-voice. You can link a server from the txAdmin console. The install guide has the details.

What You Get

• Live players and map. See who is online and where they are on the GTA map. How often positions update depends on your plan. Each player has a profile with punishments, staff notes, linked accounts and a saved route of where they have been.
• Moderation. Bans, kicks, warnings, voice and text mutes, and community service. Every one needs a reason. Bans can be sticky, which means they also cover accounts linked to the banned player.
• Bans that hold without the cloud. Your server keeps its own copy of every ban and checks joining players against it first. A ban still applies if MonoAdmin is unreachable or your server restarts.
• Player actions with honest results. Freeze, heal, revive, teleport, fun effects and vehicles, plus jobs, money and items on a framework. MonoAdmin checks the result against the game server’s own reading where it can, and shows “unknown” instead of “ok” when it cannot tell.
• Player Monitor. Watch live player screens. How many at once depends on your plan. The video goes through a relay, so the viewer and the watched player never see each other’s IP address.
• Reports and Discord Tickets. Players type /report in game (the owner switches this on) and the report carries a screenshot of what they saw. Staff answer from the panel, the in-game menu or a Discord ticket.
• In-game menu. Staff open it with /madmin or a key your project picks. It has SELF tools such as noclip, teleport, spectate, vehicles and heal or revive, and a PANEL tab with a players sheet, reports and the web panel running inside the game. The project owner switches the menu on; it is off by default.
• Character and vehicle editing. On ESX, QBCore and Qbox, edit a character’s identity, job, money, position, metadata and inventory, and their owned vehicles.
• Server tools. Announcements, shouts to one player, server-wide cleanups with a countdown, and an entity list you can delete from.
• Logs, analytics and staff activity. Server Logs put connections, kicks, staff actions, chat, commands, items and money on one timeline. Analytics show who plays, what they do and where the money goes. Staff Activity shows how active each staff member is.
• Feature switches. Turn whole modules, or single staff actions such as noclip, off for the project. Off means off for everyone, the owner included.

The Features page goes through all of it.

Built With Your Server’s Safety in Mind

• The cloud cannot push arbitrary commands to your server. Its messages go to fixed handlers, and the events a player’s game can send are a short, fixed, validated list.
• The link credential is kept in your server’s storage, never in a convar or a file you edit, and the cloud stores only a hash of it.
• Whenever a server is linked, the project owner gets an email.

The Free Starter Plan

Starter is free and has no end date. Every project starts on it. It covers up to 64 players online at once, with limits on roles, team members, Player Monitor slots and how much history is kept. If more players than that are online, most panel pages lock until the count drops.

Paid plans raise those limits and refresh the map faster. They are bought through Tebex, and a project whose paid plan ends moves back to Starter with nothing deleted. Pricing lists what each plan includes.

How to Start

1. Create an account in the panel. It is free.
2. Choose Create Server, name it and pick your framework.
3. Link your server. Get the resource from our store and the Cfx.re portal, add ensure monoadmin to server.cfg, and run monoadmin link with the code the panel shows in your server console.
4. Finish the guided setup: server icon, what MonoAdmin found on your server, features, menu key, your team and Discord tickets.

The whole install takes about five minutes. Follow it step by step in Install MonoAdmin on Your FiveM Server in Five Minutes, or read the documentation.