> For the complete documentation index, see [llms.txt](https://tk-scripts.gitbook.io/docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://tk-scripts.gitbook.io/docs/tk_bossmenu/common-questions-and-problems.md).

# Common questions & problems

Answers to the questions server owners ask most about Boss Menu on a FiveM server, and fixes for common Boss Menu problems.

## Common questions

<details>

<summary>How do I add a boss menu for another job or gang?</summary>

Copy the `police` entry in `Config.Jobs`, rename its key to the job name, and set its `permissions`, `shopItems` and `locations`. On QBCore and Qbox, a key that matches a gang in the shared gangs file makes a gang menu. [Jobs](https://tk-scripts.gitbook.io/docs/tk_bossmenu/config.md#jobs) lists every field.

</details>

<details>

<summary>How do I add grades or ranks to a job?</summary>

Grades come from your framework: on ESX edit the `job_grades` table, on QBCore and Qbox edit the shared jobs or gangs file. The menu lists new grades after `tk_bossmenu` restarts.

</details>

<details>

<summary>Why can't I open the admin menu?</summary>

Two checks must pass: the player needs the `command.bossadminmenu` ace, and their ESX group or QBCore permission must be a key in `Config.AdminGroups`. Give the ace in `server.cfg`, for example `add_ace group.admin command allow`. See [bossadminmenu](https://tk-scripts.gitbook.io/docs/tk_bossmenu/commands.md#bossadminmenu).

</details>

<details>

<summary>How do I turn off the shop, storage or wardrobe?</summary>

Remove the `orderItems`, `viewStorage` or `viewWardrobe` line from the job's `permissions` in `Config.Jobs`. A key that is missing is off for every grade, and it no longer shows on the permissions page.

</details>

<details>

<summary>Where do I collect items ordered from the shop?</summary>

At the shop ped from `Config.Shop.locations`: press the `Config.Controls.interact` key, E by default, or use the target option. Bosses order only what is in the job's `shopItems`, and a job without `shopItems` gets no pickup. When the inventory is full, what fits is handed over and the rest waits for the next visit.

</details>

<details>

<summary>Does it work with a multijob script?</summary>

Not out of the box: the menu reads and changes the one job a player has. For a multijob script, edit `SetJob` (used when the employee is online) and `FireEmployee` (used when they are offline) in `server/frameworks/esx.lua` or `qb.lua`, and `CanPlayerAccessBossMenu` and `DoesPlayerHaveMenuJob` in `server/main_editable.lua`. Off-duty job names that still count as the job go in `additionalJobs` ([Jobs](https://tk-scripts.gitbook.io/docs/tk_bossmenu/config.md#jobs)).

</details>

<details>

<summary>Is there an SQL file to import?</summary>

No. Employees and grades come from your framework's tables. Permissions set in game, statistics, notes and shop orders are saved on the server under the `tk_bossmenu` resource name.

</details>

<details>

<summary>Can I edit salaries on QBCore or Qbox?</summary>

No. The grades page shows QBCore and Qbox salaries, but they are edited in your framework's shared jobs file. On ESX, bosses with `editSalary` set them in the menu up to the job's `maxSalary`.

</details>

<details>

<summary>Does it work on Qbox?</summary>

Yes. Qbox runs the QBCore files, so set `Config.Framework = 'qb'`.

</details>

<details>

<summary>Will an update overwrite my config?</summary>

Replacing the folder replaces `config.lua` and the editable files, so back them up first. Follow [Update without losing your config](https://tk-scripts.gitbook.io/docs/tk_bossmenu/installation.md#update-without-losing-your-config).

</details>

<details>

<summary>I used tk_bosstablet. How do I move to tk_bossmenu?</summary>

Install `tk_bossmenu` as in [Installation](https://tk-scripts.gitbook.io/docs/tk_bossmenu/installation.md), remove `tk_bosstablet` from `resources` and `server.cfg`, and set it up from its own `config.lua`: the tablet item is `Config.Tablet.item` (`boss_tablet`) and the command is `/bossmenu`. `exports.tk_bosstablet:openBossMenu()` still opens the menu while `tk_bossmenu` is running.

</details>

<details>

<summary>How do I change the € sign or translate the menu?</summary>

The texts, including the € sign, are in `locales/en.lua` and `locales/fi.lua`. For another language, copy `locales/en.lua` to a new file such as `de.lua`, change `Locales['en']` on its first line to `Locales['de']`, translate the texts and set `Config.Locale = 'de'`.

</details>

## Common problems

### Money not saving or not loading/showing correctly

The company balance shows 0, a deposit disappears, or a withdrawal fails with "Not enough money".

`Config.Banking` does not match the script that holds your company money, or the job has no account in it.

* Set `Config.Banking` to your banking script ([values](https://tk-scripts.gitbook.io/docs/tk_bossmenu/config.md#framework-and-integrations)).
* ESX with esx\_addonaccount: each job needs a shared account named `society_<job>` (for police, `society_police`) in the `addon_account` table.
* A banking script that is not listed, for example ak47\_banking: edit `GetSocietyMoney`, `RemoveSocietyMoney` and `AddSocietyMoney` in `server/main_editable.lua`.

### A job shows no employees or grades

The menu opens, but a job lists 0 employees and 0 grades, and only the Home page is available.

`tk_bossmenu` reads every job's employees and grades once, when it starts. A job that is not in your framework's data at that moment stays empty until the next restart, for example when a job creator adds it later.

* Start `tk_bossmenu` after your framework, database, job creator and job scripts in `server.cfg`.
* After you add a job while the server runs, restart the resource:

  ```
  restart tk_bossmenu
  ```

### The menu says No permissions

Opening the menu with `/bossmenu`, the item or a menu location shows:

```
No permissions
```

The player's job or gang is not a key in `Config.Jobs`, or their grade is below its `open` permission.

* Add the job to [`Config.Jobs`](https://tk-scripts.gitbook.io/docs/tk_bossmenu/config.md#jobs) with the job name your framework uses.
* Lower `open` for that job, or set it on the permissions page in game. A value saved in game wins over `config.lua`.

### Permission changes in config.lua do nothing

Someone saved the permissions page in game, and those saved grades win over `config.lua`. Change the grades on the permissions page instead, as a boss with the `editPermissions` permission.

### The storage or wardrobe button is missing

The job's `permissions` has no `viewStorage` or `viewWardrobe` key, usually because the config was copied from an older version. A missing key turns the action off for every grade.

Add both keys with a minimum grade to each job in `Config.Jobs`:

```lua
viewStorage = 3,
viewWardrobe = 3,
```

### Job storage does not open

Pressing the storage quick action prints this in the F8 console:

```
[WARNING] Inventory system "default" is not supported. To fix this, open tk_bossmenu/client/main_editable.lua and edit the OpenStorage function
```

`Config.Inventory` is `'default'`, which has no stashes.

* Set `Config.Inventory` to `'ox'`, `'qb_new'`, `'qb_old'` or `'qs'`.
* Another inventory: open its stash in `OpenStorage` in `client/main_editable.lua`.

### The wardrobe does not open

Pressing the wardrobe quick action prints this in the F8 console:

```
[WARNING] Clothing script "…" is not supported. To fix this, open tk_bossmenu/client/main_editable.lua and edit the OpenOutfitMenu function
```

`Config.Clothing` is not `'esx'`, `'qb'` or `'illenium'`. Set it to your clothing script, or open your script's outfit menu in `OpenOutfitMenu` in `client/main_editable.lua`.

### ox\_lib is not loaded

With `Config.Target = 'none'`, when a player walks up to a menu location, the F8 console prints:

```
SCRIPT ERROR: @tk_bossmenu/client/main_editable.lua:77: attempt to index a nil value (global 'lib')
```

`Config.UseOxLib` is `true`, but `tk_bossmenu` does not load ox\_lib. `Config.NotificationType = 'ox'` fails the same way when a notification shows.

1. In `tk_bossmenu/fxmanifest.lua`, remove the `--` in front of `'@ox_lib/init.lua',`.
2. In `server.cfg`, put `ensure ox_lib` before `ensure tk_bossmenu`.

### The boss menu does not open from a job script

At a police or ambulance station, the ESX or QBCore boss menu opens instead, or the F8 console prints:

```
An error occurred while calling export `openBossMenu` in resource `tk_bosstablet`: Execution of function reference in script host failed:
```

`Config.Bossmenu` in the job script is not `'tk'`, or the job script calls the old `tk_bosstablet` export name, which only reaches `tk_bossmenu` while it runs under its own folder name.

* In the job script's `config.lua`, set `Config.Bossmenu = 'tk'`.
* Keep the folder name `tk_bossmenu` and start it in `server.cfg`.
* Or in the job script's `client/main_editable.lua`, call the new name in `OpenBossMenu`:

  ```lua
  exports.tk_bossmenu:openBossMenu()
  ```

### A boss cannot change or fire an employee

Promoting, demoting, hiring or firing shows one of these notifications:

```
You can't change your own grade
You can't change the grade of someone whose grade is higher than yours
You can't set someone's grade higher than your own
You can't fire this player as their grade is higher than yours
You can't fire yourself
```

A boss cannot act on their own grade, on a higher grade, or set a grade above their own. Have a boss with a higher grade make the change. When the notification is `No permission` instead, the grade is below the job's `promote`, `demote` or `fire` value ([permissions](https://tk-scripts.gitbook.io/docs/tk_bossmenu/config.md#jobs)).

### Hiring says the player is too far away

When a boss hires a player, the menu shows:

```
Player ID 12 too far away
```

The player is farther from the boss than `Config.Hiring.maxDistance`, 10 m by default. Bring them closer, or raise `maxDistance`.
