QBCore Frameworkqbcore.netCommunity docs
On this page

Updated 2026-09-21 · 5 min read

qb-management

qb-management provides job and gang employee management, boss menu locations and related stash/outfit integrations. A working boss menu requires three things to agree: the internal job or gang name, the player's current boss state, and a reachable configured location. Installing the resource alone does not establish those conditions.

Baseline: 326470f1. The README lists qb-core, qb-smallresources, qb-input, qb-menu, qb-inventory and qb-clothing; the manifest also loads oxmysql server-side. Verify the complete chain on staging.

Configure a QBCore boss menu

Use an existing valid job definition or follow job creation. Its internal key, not its label, must match Config.BossMenus. The boss flag comes from the current player job data; use job assignment to make a controlled test character rather than editing arbitrary player rows in SQL.

The following is the shape used by the pinned config:

Config.BossMenus = {
    police = {
        vector3(447.16, -974.31, 30.47),
    },
}

This is an excerpt, not a replacement for your complete menu list. Merge a location into the existing table. The coordinate is the upstream police example, not a promise that it is accessible inside your installed MLO. Walk to the location and inspect its height before concluding that a boss permission is broken.

Config.GangMenus has the corresponding gang-keyed location lists. Several upstream examples use vector3(0, 0, 0): replace those deliberately. Do not assume a listed gang has a usable office out of the box.

Enable target interactions deliberately

setr UseTarget true

Set the convar before relevant resources start. It is shared with other resources, so review the effect before changing the whole server. Start qb-target and its dependencies before qb-management in target mode.

At the pinned revision, client/cl_boss.lua creates target circles from the same Config.BossMenus coordinates. Its option requires the location's job name to match the player's job and PlayerJob.isboss to be true. The target circle has radius 0.5, uses Z and has an interaction distance of 2.5 at this baseline.

With target mode off, the client uses proximity checks and an interaction prompt instead. Do not copy an unrelated fork's BossMenuZones table into this revision and expect its client to read it.

Inspect the live job before changing permissions

For a staging-only client diagnostic, place this in your own started client resource with qb-core declared as a dependency:

local QBCore = exports['qb-core']:GetCoreObject()

RegisterCommand('qbnet-jobcheck', function()
    local job = QBCore.Functions.GetPlayerData().job
    if not job then
        print('[jobcheck] No loaded job data yet.')
        return
    end

    local grade = type(job.grade) == 'table' and job.grade.level or 'unknown'
    print(('[jobcheck] name=%s grade=%s isboss=%s'):format(
        tostring(job.name), tostring(grade), tostring(job.isboss)
    ))
end, false)

Run /qbnet-jobcheck in in-game chat and read F8. This only inspects the local player; it does not grant a job or authorize an action. A changed shared definition and the already-loaded player's current data are different things. Reapply the intended job/grade through the normal administration flow and reconnect on staging when checking changes.

The reference for the inspected state is the pinned boss-menu client and QBCore functions. Do not leave debugging commands in a production customization by accident.

Verify permissions and employee changes

Prepare a boss, a non-boss employee and an unrelated character. Confirm the intended job names and grades before opening the menu. Then test one employee operation at a time, checking the resulting server state and reconnect behavior.

ScenarioExpected result
Boss at the configured locationCan open the correct organization's menu
Same job without boss statusCannot manage employees through that menu
Boss of a different organizationDoes not gain management access to this location's job
Hire a test characterIntended job and starting grade are applied
Change an allowed gradeEmployee state matches the selected valid grade
Remove the test employeeIntended removal/unemployed behavior occurs
Inspect an offline employeeSupported offline flow works without damaging unrelated records
Open boss stash and outfitsCompatible inventory/clothing integrations respond

The UI's isboss condition is not a server authorization audit. Preserve and review checks on the requester, target employee, organization and grade in every server handler you adapt. Manual scenarios here are not evidence that they have already run or that upstream is secure by default.

Troubleshooting

SymptomCheck firstAvoid
No interaction at allActual coordinates/Z, selected target mode and startup errorsGranting broader staff permissions
Employee sees the location but not the menuLive job.name and job.isbossTrusting only the displayed rank label
Target appears but opening failsqb-menu/qb-input startup and the first client errorInstalling another boss menu over this one
Hire or grade change failsServer validation, allowed grades, database errorsEditing player records blindly
Society money functions are missingYour qb-banking integrationAssuming an old management fork's exports exist
Stash behavior changes after an updateInventory API and ownership checks at both revisionsReplacing storage handlers as a UI fix

Update checklist

Record resource revisions and back up the affected data. Diff config, employee handlers, database calls and integrations together. Run the role matrix and hire/change/remove sequence on staging, including reconnects. Keep the previous code and a reviewed recovery plan before production rollout.

Remove the temporary diagnostic and restore only your intentional configuration changes to roll back the setup experiment. Do not overwrite newer employee data with an old full database snapshot merely to undo a menu-coordinate change. Continue with safe resource updates or resource references.

Found an issue in this guide?

Send the page URL, the affected example, and a source or reproduction to the site maintainer. For a server or resource problem, use the support guide.

On this page

Leonida RP server website built with RPWebsite
RPWebsite

Advertisement · RPWebsite

Want a website for your server?

Launch a site with live player status, rules, and a join button in minutes.

Build your website