Updated 2026-10-11 · 2 min read
qb-cityhall: license issuance and job applications
qb-cityhall provides a city-hall interface for identity documents, driving and weapon licenses, and public job applications. The current reference is pinned to commit 020f041. It does not provide the police-side authorization to grant a weapon license.
Installation and dependencies
Start qb-core, qb-inventory and the relevant interaction/resource dependencies before qb-cityhall. The bundled client.lua opens menus and handles NPC interaction, while server.lua handles job and item operations.
Config.UseTargetfollows theUseTargetserver convar.Config.AvailableJobslists publicly available jobs such astaxi,truckerandbuswhen not usingqb-jobs.Config.Cityhallslists hall positions and purchasablelicenses.Config.DrivingSchoolsconfigures instructor IDs and driving-school positions.Config.Pedsconfigures NPC models, positions and interaction zones.
License configuration
The upstream config includes these document keys:
| Item key | Default cost | Eligibility |
|---|---|---|
id_card | 50 | Public |
driver_license | 50 | Player metadata licences.driver |
weaponlicense | 50 | Player metadata licences.weapon |
The upstream item is named weaponlicense, while the eligibility metadata uses weapon. Buying a hard-copy document is different from receiving the underlying permission. For the end-to-end flow, use the weapon-license guide.
Integration surface
The server exports AddCityJob(jobName, toCH). A job object requires label and isManaged and the export returns success/status. This changes the resource's runtime job list; it does not automatically create a QBCore shared job definition.
-- Only after the 'delivery' job exists in qb-core and your server has
-- configured its grades, payroll and permissions:
local ok, reason = exports['qb-cityhall']:AddCityJob('delivery', {
label = 'Delivery Driver',
isManaged = false,
})
print(ok, reason)Bundled QBCore callbacks: qb-cityhall:server:receiveJobs and qb-cityhall:server:getIdentityData.
Server network events: qb-cityhall:server:requestId, qb-cityhall:server:sendDriverTest, qb-cityhall:server:ApplyJob and qb-cityhall:server:getIDs. The getIDs event invokes the bundled starter-item issuance handler; it is not registered with CreateCallback.
These are internal menu operations, not permission-granting public APIs. In the reviewed implementation, requestId indexes a client-supplied hall/license entry without a complete independent eligibility check. Validate any externally exposed purchase flow server-side before depending on it for restricted documents.
Troubleshooting
| Symptom | First check |
|---|---|
| Weapon/driver license not offered | Metadata licences and the selected hall's configured licenses |
| Document cannot be purchased | Cash balance, exact item name in shared items and qb-inventory |
| City job missing | Config.AvailableJobs, qb-jobs integration and availability callback |
| NPC/menu not visible | UseTarget convar, Config.Peds zones and resource startup |
| Item has incorrect personal data | charinfo on the loaded QBCore player and document item metadata |
Update checklist
- Compare installed city-hall code with the pinned upstream configuration and server handlers.
- Test license visibility with and without player eligibility.
- Test ID issuance and job application from an allowed and an unauthorized character.
- Do not add new purchase/permission events without server-side authorization checks.
Sources
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.
