Player Management

Every moderation action in one browser tab

FiveGateway gives staff a single search bar over every player who has touched your server. Live presence, full history, bans, warnings, whitelist, and remote screenshots live on one page, usable from any device, no game client required.

The online players view is the default landing zone for moderators. It lists every connected player with their identifier, ping, session length, and the actions you can take: kick, take a remote screenshot, open their full profile. Screenshots are captured through the FiveM native and stored as thumbnails on the player's timeline, so suspicious behavior becomes evidence instead of memory.

Search works across every identifier FiveM hands you: license, Steam ID, Discord ID, IP, and any custom fingerprint your framework stores. That matters because multi-account users do not respect clean data: a player who smurfs across three Steam accounts still has one Discord ID, and a good search finds them all.

Bans, warns, and kicks are first-class records, not log lines. Each one ties to an actor (the admin who placed it), a reason, a player, and a timestamp. You can appeal, lift, or extend a ban from the player profile, and the change is written back to a history that your whole team can audit. If you also run txAdmin, the existing txAdmin bans sync automatically with no migration needed.

Whitelist management goes beyond a binary list. You can run the server in open mode, whitelist-only mode, or maintenance mode from the dashboard, and the queue system respects those states without restart. Adding a player to the whitelist takes one click from their profile, and the reason field keeps a written record of why the slot was granted.

Remote screenshots are the unsung hero. Because they fire through the FiveM API over your existing WebSocket connection, any admin on any device can request a screenshot of any online player in under a second. That closes the gap between a player reporting someone and you having proof, with no need to have a second admin in-game.

All of this is gated by role-based permissions. A junior moderator can kick and warn but not permaban; a senior admin can do everything; a community manager might only have read access. Permissions map onto your Discord roles when the Discord bot is linked, so onboarding new staff is a role assignment in Discord, not a fresh FiveGateway login.

How it works

  1. 1

    Connect your server

    Install the FiveGateway resource on your FiveM server. Players appear in the online view the moment they join.

  2. 2

    Search across identifiers

    Use any identifier FiveM exposes: license, Steam, Discord, IP. The dashboard matches across all of them.

  3. 3

    Apply actions with reasons

    Ban, warn, kick, or whitelist from the player profile. Every action is logged with the actor and reason for later audits.

Related