Documentation
Follow the installation steps to get the script running quickly and correctly on your server, with everything you need to get started.
Before installing Quasar Job Management, make sure your server meets the minimum requirements. The resource requires OneSync, a working MySQL database, and both ox_lib and oxmysql installed and running.
If you're using a modern ESX, QBCore, or QBox server, these dependencies are usually already installed.
Requirement | Status | Download |
|---|---|---|
| Required | https://github.com/overextended/ox_lib |
| Required | https://github.com/overextended/oxmysql |
OneSync | Required | Enabled in your server settings |
Quasar Job Management automatically detects your framework (ESX, QBCore or QBox) through Config.Framework. ox_lib provides the callbacks and notifications used across the resource.
After purchasing Quasar Job Management, the resource is automatically linked to your CFX Portal account.
Sign in to the CFX Portal using the same account used during checkout, then open Granted Assets and locate Job Management in your asset library. Download the latest version and extract the archive.
After extracting the download, you should have the following folders:
qs-job-management
[sql]Folder | Description |
|---|---|
| Main resource (required). |
| SQL file. |
Never rename the resource folder. The resource checks its own name on startup: renaming it freezes the server thread and spams the console. It must remain
qs-job-management.
The [sql] folder is not a resource and must not be placed inside your resources directory.
Move the qs-job-management folder into your server's resources directory. Although the resource can be placed anywhere inside the folder, keeping Quasar resources organized inside their own directory is recommended.
A typical installation looks like this:
resources/
└── [quasar]/
└── qs-job-management/Once the resource has been copied, open your server.cfg and ensure every required dependency starts before Quasar Job Management.
ensure oxmysql
ensure ox_lib
# Framework
ensure es_extended
# ensure qb-core
# ensure qbx_core
ensure qs-job-managementThe loading order matters. Always start your framework, oxmysql and ox_lib before starting qs-job-management.
Quasar Job Management stores each player's jobs, grades and badges in the qs_job_management table.
No manual SQL import is required. The table is created automatically on the first startup, and any missing column is added automatically when updating from an older version. The
[sql]/qs-job-management.sqlfile is optional, and only included for servers that prefer to create the table by hand.
Everything else — treasury, contracts, permissions, salaries, stats and logs — is stored in JSON files inside the resource's data/ folder, not in the database.
This step is important before going live. The data/*.json files ship with data from the development server — treasury balances, reports, stats and logs.
Empty them before opening your server:
bosses.json → (empty)
hrlog.json → (empty)
data/bosses.json → {}
data/bosslocations.json → []
data/contracts.json → {"list":[],"nextId":1}
data/hire_modes.json → {}
data/jobpermissions.json → {}
data/jobstats.json → {}
data/playerreports.json → {}
data/rank_salaries.json → {}
data/salary_config.json → {}
data/serverlogs.json → []Skipping this leaves fake balances and logs visible in your boss and admin panels.
Open config/config.lua and set at least:
Config.Locale = "en" -- locales/ has 19 languages
Config.Jobs = { ... } -- the jobs the menu knows about, with icons and badges
Config.BossLocations = { ... } -- where each job's boss panel can be opened
Config.MaxJobs = 5 -- jobs a player may hold at once
Config.Interactions = { ... } -- commands and keys
Config.DiscordWebhook = "" -- leave empty to disable loggingYou never register jobs by hand. The resource listens for your framework's job events, so whatever gives a player a job — a job center, an admin command, another script — is picked up automatically. Config.Jobs only defines how each job is displayed in the menu.
After completing the installation, restart your FiveM server.
Join your server and execute the following command:
/jobIf the job menu opens and lists your current job, Quasar Job Management has been installed correctly and your server is ready to go.
To verify the admin panel, use an account with the ESX group admin / superadmin or the QBCore permission admin, and run:
/boss