> ## Documentation Index
> Fetch the complete documentation index at: https://docs.redutzu.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Configuration

> Configure redutzu-mdt in-game with the admin panel.

Most of the MDT is configured in-game from the admin panel. You don't need to edit `config.lua` or restart the server for these settings.

![redutzu-mdt admin panel showing the Access section](https://mintcdn.com/redutzusscripts/jYySSRvwCjpWaAJk/images/mdtadmin.webp?fit=max\&auto=format\&n=jYySSRvwCjpWaAJk\&q=85\&s=ccf5eb203ff93a0fbf2b243938136130)

The admin panel, opened on the Access section

## Open the admin panel

Run `/mdtadmin` in-game. The panel opens for any admin, whatever their job.

| Framework | Who counts as an admin |
| - | - |
| ESX, QBCore, Qbox | Players in a group listed in `Config.AdminGroups` (`admin`, `god` by default) |
| Standalone, custom | Players with the `redutzu_mdt.admin` ACE |

On standalone servers, add this line to your `server.cfg`:

```cfg server.cfg theme={null}
add_ace group.admin redutzu_mdt.admin allow
```

> [!TIP]
>
> To rename the command or turn it off, edit `Config.AdminCommand` in `config/config.lua`.

## How settings are saved

* Changes apply instantly and sync to every player.
* The MDT saves them in the database, so they stay intact when you update the script.
* Panel values override `config.lua`. Anything you never changed in the panel keeps its `config.lua` value.
* Use **Reset section** to send a section back to its `config.lua` values.

## Sections

### Setup

| Section | What you configure |
| - | - |
| **Access** | Who can open the MDT, how they open it, and which department sees which records. |
| **Permissions** | What each rank of each job is allowed to do inside the MDT. |
| **General** | Language, date and number formats, officer statuses, and the nationalities list. |
| **Interface** | The default theme and your own pages in the sidebar. |
| **Integrations** | Which of your server's resources the MDT works with. Read-only, set in `config.lua`. |

### Records

| Section | What you configure |
| - | - |
| **Records** | What officers see on citizen and vehicle records, vehicle modification categories, page sizes, and log retention. |
| **Evidence** | Evidence types, lab analyses, and where logged items are stored. |

### Justice and money

| Section | What you configure |
| - | - |
| **Justice** | The highest punishments a charge can carry, and the license points system. |
| **Money** | Where fine money goes, the officer's share, and how bills are handled. |

### Operations

| Section | What you configure |
| - | - |
| **Communications** | MDT chat and channels, private messages, automatic chat posts, and radio codes. |
| **Dispatch** | How crimes turn into dispatch calls, how calls behave, and what officers see on the map. |
| **Units** | Unit types, automatic statuses on calls, vehicles, zones, and dispatch stats. |
| **Field units** | The plate reader (radar) and police dogs. |
| **Cameras** | CCTV cameras, bodycams, and dashcams: damage, repairs, hacking, sound, recordings, and activation. |
| **CCTV manager** | Every placed CCTV camera: find it on the map, teleport to it, edit or move it, and copy camera layouts. |

> [!TIP]
>
> Use the search bar at the top of the panel to jump straight to any setting.

## Move settings between servers

Use the buttons at the bottom of the panel to copy your setup to another server, such as from a test server to production.

**1. Export**

Click **Export settings**. Every setting you changed is copied to your clipboard.

**2. Import**

On the other server, click **Import settings** and paste the text. You see every change before anything is saved. If one value is invalid, nothing is saved.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.