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

# Commands, keybinds & permissions

## Commands and default keys

All names and keys are set in `config.lua` (`Config.Editor` and `Config.Commands`). Keys are registered with FiveM key mapping, so each player can rebind them in **Settings > Key Bindings > FiveM**.

| Command       | Default key | What it does                                                     |
| ------------- | ----------- | ---------------------------------------------------------------- |
| `/hud`        | **F7**      | Opens the HUD editor.                                            |
| `/togglehud`  | none        | Shows / hides the HUD.                                           |
| `/cinematic`  | none        | Cinematic mode (black bars + HUD hidden).                        |
| `/carcontrol` | none        | Car control panel (doors, windows, engine, lights, seats).       |
| `/seatbelt`   | **B**       | Fastens / unfastens the built-in seatbelt.                       |
| `/cruise`     | none        | Built-in cruise control (minimum `Config.Vehicle.cruiseMinKmh`). |
| `/limiter`    | none        | Built-in speed limiter (minimum `Config.Vehicle.limiterMinKmh`). |

{% hint style="info" %}
Set a key with the matching `...Key` option, for example `Config.Commands.cruiseKey = 'X'`. Set a command to `''` to disable it.
{% endhint %}

## Editor shortcuts

| Keys            | Action                                 |
| --------------- | -------------------------------------- |
| Ctrl+Z / Ctrl+Y | Undo / redo                            |
| Esc             | Go back (on Home it closes the editor) |
| Hold Space      | See the HUD without the editor window  |

## Permissions

Players need no permission to use and customize their own HUD (unless the HUD is locked).

**HUD admins** can publish and remove the **server layout** from `/hud` > Share > Server. A player is a HUD admin if they:

1. have the ACE `ghiaccio_hud.admin`, **or**
2. belong to one of the groups in `Config.AdminGroups` (`config_server.lua`, default `{ 'admin', 'superadmin' }`).

The check is always done by the server, never by the client.

```cfg
add_ace group.admin ghiaccio_hud.admin allow
```

{% tabs %}
{% tab title="ESX" %}
`Config.AdminGroups` is compared with the player group (`xPlayer.getGroup()`: `'admin'`, `'superadmin'`, ...).
{% endtab %}

{% tab title="QBCore" %}
`Config.AdminGroups` is checked with the framework permissions (`QBCore.Functions.HasPermission`: `'admin'`, `'god'`, ...).
{% endtab %}

{% tab title="Qbox" %}
`Config.AdminGroups` is checked with the framework permissions (`HasPermission`).
{% endtab %}

{% tab title="Standalone" %}
`Config.AdminGroups` is checked as ACE groups `group.<name>`:

```cfg
add_principal identifier.license:YOUR_LICENSE group.admin
```

{% endtab %}
{% endtabs %}

An empty list `{}` means ACE only. A wrong group name grants access to nobody.

### Locking the HUD

With `Config.ServerDefault.locked = true` (`config_server.lua`) **non-admin** players cannot edit the HUD: `/hud` shows "This server's HUD is locked: you cannot edit it.", personal saves are rejected by the server too, and they always see the server layout (or the factory one if none exists). Admins can always edit and publish.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://ghiaccioscripts.gitbook.io/ghiaccioscripts-docs/hud/commands-and-permissions.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
