Bablo ResourcesDocs

Permissions

Every grade of a job carries its own set of permissions, edited in-game in the Grades & Permissions tab or the Boss Creator. All checks run server-side — the UI only hides what a player can’t use.

Permission keys

KeyGrants
view_statisticsView dashboard statistics and the attendance chart
view_transactionsView the transaction history and chart
deposit_moneyDeposit money into the society account
withdraw_moneyWithdraw money from the society account
hire_employeesHire nearby players into the job
fire_employeesFire employees (online or offline)
promote_employeesPromote or demote employees
order_itemsOrder items from the job store
manage_upgradesManage store purchases
edit_permissionsEdit grades, permissions, salaries and profile settings
manage_accessGrant or deny individual employees access to stashes, the wardrobe and the shop

Tab visibility

TabShown with
Dashboardview_statistics, view_transactions, deposit_money or withdraw_money
Employeeshire_employees, fire_employees or promote_employees
Grades & Permissionsedit_permissions
Shop Systemorder_items or manage_upgrades, unless an individual override says otherwise
Wardrobewardrobe access (see Menu access)
Profilealways visible to anyone who can open the menu

Full access

A player bypasses per-permission checks entirely when any of these is true:

  • they hold the job’s highest grade (the boss rank), or
  • their grade is in the job’s Boss Menu Access list set in the creator, or
  • the framework marks them as boss (isboss on QBCore/Qbox).

The boss rank’s full permission set is enforced automatically — even if a save tried to strip it, the server restores every key for the top grade.

The Edit Grade dialog carries a Menu access section below the permission toggles:

  • Wardrobe — whether the grade can use wardrobe points and equip job outfits.
  • One toggle per placed stash — whether the grade can open that specific stash, so a sensitive evidence or supply stash can be limited to the ranks that actually need it.

By default everything is on: a job with untouched menu access behaves exactly as before. The lists follow grade renumbering automatically, and the shop keeps using the order_items / manage_upgrades permissions instead of a separate toggle.

Per-employee overrides

With the manage_access permission (or full access), the Employees page gets a Manage Access action. It opens a dialog with Default / Allow / Deny for the wardrobe, the shop and each placed stash:

  • Default — the employee follows their grade’s rules.
  • Allow — access is granted even if their grade doesn’t have it.
  • Deny — access is blocked even if their grade has it.

Overrides beat grade rules; full-access players always pass regardless of overrides. The server refuses changes to your own access or to anyone at or above your rank, and a fired employee’s overrides are deleted automatically.

All of it is enforced server-side — stash opens, store purchases and wardrobe opens resolve through the same check, and on ox_inventory the stash itself is registered to the job with an open hook applying the same rules, so the inventory cannot be opened around the menu.

Hierarchy rules

Permissions alone aren’t enough — rank matters too:

  • You can only fire, promote, demote or set salaries for grades below your own (full-access players are exempt).
  • You can’t fire yourself or change your own grade.
  • Salary changes are always capped by Settings.SalaryLimit; without full access they can only target grades below your own.

Who can open the menu?

A placed boss menu location is usable by: the grades selected under Boss Menu Access, plus every grade that has at least one permission, plus always the highest grade. Employees without any of that can still use the job’s stash and wardrobe locations — those require holding the job and passing the menu access rules above.