[GUIDE]

FiveM QBCore Roster System

PulseRoster is a standalone FiveM roster tool that works alongside QBCore, QBox, or any other framework. It handles the HR side — ranks, certifications, LOA, discipline, activity tracking — while QBCore keeps doing what QBCore does in-game.

No server-side install. No framework conflicts. Works via Discord integration.

How a QBCore server uses PulseRoster

QBCore is your in-game framework. It handles jobs, money, inventory, and gameplay state. PulseRoster is your out-of-game personnel system. It handles the human side of your community — who's an officer, who's in SWAT, who's on LOA, who's been promoted, who's meeting activity requirements.

The two systems connect through Discord. PulseRoster syncs ranks to Discord roles automatically. If you also use a Discord-to-QBCore bridge (there are several popular ones), those Discord roles can trigger in-game job grade changes. Or, most commonly, servers just handle in-game jobs and out-of-game roster separately — they serve different purposes and rarely need to be tightly coupled.

QBCore handles

  • • In-game jobs
  • • Money & inventory
  • • Vehicles & housing
  • • Gameplay scripts

PulseRoster handles

  • • Personnel & ranks
  • • Certifications
  • • Activity tracking
  • • LOA & discipline

Discord bridges

  • • Role sync (built-in)
  • • OAuth login
  • • Slash commands
  • • Webhook alerts

What you don't need to do

Because PulseRoster is framework-agnostic, you don't have to:

  • Install any FiveM resource or script
  • Modify QBCore shared files or job configs
  • Add tables to your MySQL database
  • Worry about compatibility with QBCore updates
  • Rebuild your in-game job structure to match PulseRoster's ranks

Your FiveM server keeps running exactly as it does. PulseRoster lives at roster.mypulsetech.com and your members access it via Discord OAuth — they don't need a separate account.

Setting it up on a QBCore server

  1. 1Create a PulseRoster community at roster.mypulsetech.com/register. Free tier covers 3 departments and 25 members.
  2. 2Connect your Discord server so OAuth login works and role sync can push rank changes to Discord automatically.
  3. 3Create your departments — typically LSPD, BCSO, EMS, Fire, and whatever civilian factions your server runs. Match the ranks your community already uses.
  4. 4Import your existing roster via CSV (on Standard/Pro tiers) or add members manually. Discord handles will map to existing Discord accounts automatically.
  5. 5Configure Discord role mappings — tell PulseRoster which Discord role corresponds to each rank. From then on, promotions in PulseRoster sync to Discord automatically.

Most QBCore servers are fully set up in under 30 minutes. See the full setup guide for step-by-step instructions.

Common Questions

Does PulseRoster require QBCore, or does it work with any FiveM framework?
PulseRoster is framework-agnostic. It works with QBCore, QBox, ESX, vMenu, and standalone FiveM servers. The integration happens via Discord role sync — PulseRoster manages the personnel side (ranks, LOA, certifications, activity) and your in-game framework (QBCore) keeps handling jobs and money. The two systems coexist cleanly.
How does PulseRoster work with QBCore jobs?
You keep QBCore jobs exactly as they are in-game — police, ambulance, mechanic, etc. PulseRoster sits alongside as the HR/personnel system. When someone gets promoted in PulseRoster, their Discord role updates, and you can use any Discord-to-QBCore bridge to sync that Discord role to an in-game job grade. Many servers just manage the in-game side separately.
Do I need to install anything server-side for PulseRoster to work with QBCore?
No. PulseRoster is a web application with Discord integration. There are no FiveM resources to install, no QBCore shared code to modify, no database tables to add. It operates entirely outside your FiveM server and connects through Discord and optionally a webhook.

Run a QBCore server? Try PulseRoster free.

No server-side install. No framework conflicts. Connect Discord, create departments, invite members. You'll be up and running before your next dev meeting.