> 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/police-and-medical/cuxial-police.md).

# Cuxial Police

MDT for police, EMS and a federal agency: tablet, quick menu, radio, dispatch and live admin settings.

Cuxial Police is a mobile data terminal (MDT) shared by three factions: police, EMS and an optional federal agency. Each faction gets its own tablet theme, tabs, radio, dispatch and roster, and staff edit almost every setting from inside the tablet, without touching files.

## What it does

* **Tablet (MDT)** with citizens, vehicles, reports, penal code, wanted list, debtors, prison management, cameras, time control and staff management.
* **Quick menu** for field work: cuff, escort, frisk, seize, put in vehicle, place objects, traffic control points, lockpick and ankle monitor.
* **Radio** on `pma-voice`, with tactical frequencies, a command tier and its own audio effect.
* **Dispatch** sidebar and a **Central** board, fed by gunshot alerts, the `/entorno` command and any resource through an export.
* **EMS module**: patient files, prescriptions, treatments, pharmacy, billing catalogue, appointments agenda, obstetrics and morgue.
* **Federal agency addon** (third faction): case files, subjects of interest, criminal organisations, judicial warrants, operations and surveillance devices.
* **Fines and medical bills** paid by the citizen at payment points.
* **Built-in prison** with sentences that only count down while the inmate is online.
* **Station points** created in game: duty, stash, armoury, MDT terminal or a custom event, as a target zone or as an NPC.
* **Admin settings** in the tablet: every option is stored in the database and most of them apply live.

How each part is used in game is explained in the [Features guide](/scripts/police-and-medical/cuxial-police/features.md).

## Requirements

| Resource              | Required    | Used for                                                        |
| --------------------- | ----------- | --------------------------------------------------------------- |
| `ox_lib`              | Yes         | Callbacks, keybinds, locales, notifications                     |
| `oxmysql`             | Yes         | All data and the settings                                       |
| `cuxial_bridge`       | Yes         | Connects to your framework, inventory and target                |
| `pma-voice`           | Yes         | Faction radio and hidden microphones                            |
| `ox_inventory`        | Recommended | Items, stashes, armouries, evidence, medicine checks            |
| `screencapture`       | No          | Mugshots, vehicle photos and photo proofs                       |
| `cuxial_medical`      | No          | EMS actions of the quick menu (examine, CPR, heal, stretcher)   |
| `cuxial_diseases`     | No          | Diseases, vaccines and cure plans in the patient file           |
| `cuxial_gang`         | No          | Organisations, intelligence and operations of the federal addon |
| `cuxial_banking`      | No          | Sends paid fines and bills to the faction account               |
| `cuxial_license`      | No          | Licences in the citizen file                                    |
| `cuxial_garages`      | No          | Impound menu and vehicle state                                  |
| `cuxial_interactions` | No          | Station points as NPCs with dialogue                            |
| `lb-phone`            | No          | SMS and e-mail reminders for medical appointments               |
| `rcore_prison`        | No          | Replaces the built-in prison when it is running                 |

{% hint style="warning" %}
Cuxial Police is built on QBox with `ox_inventory`, and runs on QBCore and ESX through `cuxial_bridge`. Two features have their own requirement: changing a rank from the staff page requires a framework with multi-job support, and duty on ESX requires a version whose jobs carry an on-duty state.
{% endhint %}

## Pages

<table data-view="cards"><thead><tr><th></th><th></th><th data-hidden data-card-target data-type="content-ref"></th></tr></thead><tbody><tr><td><strong>Installation</strong></td><td>Dependencies, items, convars and start order.</td><td><a href="/scripts/police-and-medical/cuxial-police/installation.md">Installation</a></td></tr><tr><td><strong>Features guide</strong></td><td>The three factions and the modules each one has.</td><td><a href="/scripts/police-and-medical/cuxial-police/features.md">Features guide</a></td></tr><tr><td><strong>Configuration</strong></td><td>The settings panel and every section it holds.</td><td><a href="/scripts/police-and-medical/cuxial-police/configuration.md">Configuration</a></td></tr><tr><td><strong>Commands &#x26; permissions</strong></td><td>Commands, default keys and grade permissions.</td><td><a href="/scripts/police-and-medical/cuxial-police/commands.md">Commands &amp; permissions</a></td></tr><tr><td><strong>Exports &#x26; events</strong></td><td>Send alerts, read duty and jail players from your resources.</td><td><a href="/scripts/police-and-medical/cuxial-police/developers.md">Exports &amp; events</a></td></tr><tr><td><strong>Troubleshooting</strong></td><td>Common problems and how to fix them.</td><td><a href="/scripts/police-and-medical/cuxial-police/troubleshooting.md">Troubleshooting</a></td></tr></tbody></table>


---

# 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/police-and-medical/cuxial-police.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.