> For the complete documentation index, see [llms.txt](https://docs.cuxial.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.cuxial.com/scripts/gangs/cuxial-gang/commands.md). # Commands & permissions Commands, keys and permissions of Cuxial Gang, for staff, organizations and police. Who can run each command of Cuxial Gang, which keys it registers and how staff and rank permissions work. ## Staff commands | Command | Who | What it does | | ----------------------------------------- | ---------------------------- | ---------------------------------------------------------------------------------------------------------------------------------- | | `/crimeadmin` | Staff | Opens the staff panel. | | `/setcrimejob ` | Staff | Puts a player into an organization. `` is `boss` (top rank) or `recruit` (lowest rank). | | `/firemember ` | Staff | Removes a player from their organization. | | `/addcrimecar ` | Staff, `group.admin` | Gives an organization a vehicle. The model must exist in the vehicle catalogue of the staff panel. | | `/resetgangstats` | Staff, `group.admin` | Sets captured zones and missions done to zero for every organization, and clears the loyalty of all turf zones. | | `/startAirDrop` | Framework permission `admin` | Launches a normal airdrop. | | `/testairdrop [tier]` | Framework permission `admin` | Launches a test airdrop 15 metres in front of you. `[tier]` is `bronze`, `silver`, `gold` or `diamond`; the first tier if omitted. | | `/approveraid ` | Staff, `group.admin` | Approves a raid of that job on that organization. Only with `adminMode.enable = true` in `data/raids.lua`. | | `/spawntestnpc` | Staff, with debug on | Spawns a test hostage NPC in front of you. Only exists with `debug = true`. | | `/cleartestnpcs` | Staff, with debug on | Removes the test NPCs you spawned. Only exists with `debug = true`. | {% hint style="info" %} `` is the numeric id of the organization, shown in the staff panel. The first five commands can be renamed or removed in the `commands` block of `shared/config.lua`; the airdrop commands in `data/airdrop.lua` and the raid commands in `data/raids.lua`. The staff commands also run from the server console. {% endhint %} ## Player commands | Command | Who | What it does | | --------------------- | --------------------- | -------------------------------------------------------------------------------------------------------------------------------- | | `/crimetablet` | Members and mules | Opens the tablet. Does not exist with `tablet.asItem = true`. The name is set in `tablet.command`. | | `/mulapaso` | Mules | Marks the current step of the active contract as done. The name is set in `StepCommand` of `data/mulas.lua`; `false` removes it. | | `/startraid ` | Jobs in `allowedJobs` | Starts a raid on an organization. Only with `enable = true` in `data/raids.lua`. | ## Keys | Key | What it does | | ---------------------- | ------------------------------------------------------------------------------------------------ | | F6 | Opens the interaction menu on the nearest player. Members only. Default from `rope.keybind.key`. | | Right Shift | Brings back the staff panel after minimizing it. | Each player can rebind both in the GTA settings, under key bindings for FiveM. A changed default only applies to players who have not joined before. ## Staff permission Staff is whoever has the ACE named in `admin.ace`, `mod` by default. The panel, every action inside it and the staff commands check it on the server. {% code title="server.cfg" %} ```cfg add_ace group.mod mod allow add_principal group.admin group.mod ``` {% endcode %} Commands also carry a group in `restricted`. That group decides who sees and can type the command; the ACE decides whether it does anything. A staff member needs both. | Command | Group by default | | ------------------------------------------------- | ---------------- | | `/crimeadmin`, `/firemember`, `/setcrimejob` | `group.mod` | | `/resetgangstats`, `/addcrimecar`, `/approveraid` | `group.admin` | The airdrop commands have their own rule: each one requires the framework permission set in `permission` of `data/airdrop.lua` (`'admin'` by default), checked through `cuxial_bridge`. ## Rank permissions Inside an organization, the boss ticks permissions for each rank in the boss menu. The top rank of a new organization starts with all of them. | Permission | Allows | | --------------------- | --------------------------------------------------------------------------------------------- | | `bossmenu_access` | Open the boss menu and manage members, ranks, upgrades, vehicles, mules and cloakroom outfits | | `garage_access` | Use the garage | | `storage_access` | Open the stash and the extra stashes | | `blackmedic_access` | Use the clandestine medic | | `moneylaundry_access` | Run the money laundering route | | `port_access` | Use the port | ## Police | Feature | Requirement | | --------------------------- | ---------------------------------------------------------------------------------------------------------------------------------- | | Start a raid | Job listed in `allowedJobs` with at least `minimumGradeToStart`; on duty with `requireDuty = true`; inside the hours of `raidTime` | | Seize a cartel supply point | Job listed in `seize.jobs` of `data/supply.lua`, or the raid jobs when it is `nil`; on duty with `seize.requireDuty = true` | --- # 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://docs.cuxial.com/scripts/gangs/cuxial-gang/commands.md?ask=&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.