Pages - Redutzu Docs

Disable pages

Hide pages your server doesn’t use, such as Cameras or Radio. Disabled pages disappear from the sidebar for everyone, and links to them open the home page instead. Their data is kept, so you can turn a page back on any time.

Admin panel
config.lua

Open Interface

Run /mdtadmin and open Interface.

Hide pages

Under Disabled pages, pick each page to hide.

Disabled pages picker in the admin panel — Hiding pages in the Interface section

The sidebar updates instantly for every officer.

config/config.lua

Config.DisabledPages = { 'cameras', 'radio' }

Restart the resource to apply the change.

Page names

dashboard, dispatch, radio, cameras, announcements, incidents, evidences, warrants, bolos, citizens, vehicles, houses, weapons, officers, penalcode, penalties, prisoners, operationplans, templates, logs, employees, management, config

To hide a page from only some ranks, don’t disable it. Remove its .view permission from those grades instead. See Permissions.

Add your own pages

Custom pages open a website inside the MDT, such as a department wiki, rules, or your own tool. Each page gets its own entry in the sidebar.

MDT showing a custom page and its sidebar entry — A custom page open in the MDT

There are two ways to add one:

Method	Use it for
Admin panel or config	A website that’s already online, such as a Google Doc or wiki.
`RegisterPage` export	A page built into your own FiveM resource.

From the admin panel or config

Admin panel
config.lua

Open Interface

Run /mdtadmin, open Interface, and find Custom pages.

Add a page

Fill in the name, sidebar text, and website address. The other fields are optional. The preview shows how the sidebar will look.

Choose who sees it

Pick a permission, or type your own, such as wiki.view. Leave it empty to show the page to every officer.

Custom pages form in the admin panel — Adding a custom page, with the sidebar preview

config/config.lua

Config.CustomPages = {
    {
        name = 'handbook',
        label = 'Handbook',
        url = 'https://docs.example.com/handbook',
        icon = 'book-open',
        category = 'department',
        title = 'Department handbook',
        subtitle = 'Rules and procedures',
        permission = 'handbook.view'
    }
}

Restart the resource to apply the change.

Field	Required	Description
`name`	Yes	Unique id, used in the page’s address. Lowercase letters, numbers, `_`, and `-`.
`label`	Yes	Text shown in the sidebar.
`url`	Yes	Website to open. Starts with `https://`.
`icon`	No	A Lucide icon name, such as `book-open`.
`category`	No	Sidebar group. Pages with the same category are listed together. Defaults to `custom`.
`title`	No	Heading above the page. Defaults to `label`.
`subtitle`	No	Small text under the heading.
`permission`	No	Permission needed to see the page. Empty shows it to every officer.

Some websites block being shown inside other pages, such as most Google pages and sites with strict security headers. If a page stays blank, open the browser console with F8 to check. Use a site that allows embedding, or host the page in a resource.

From a resource

Call RegisterPage on the client to add a page from your own resource. The page is removed automatically when your resource stops.

client.lua

exports['redutzu-mdt']:RegisterPage({
    name = 'my-plugin',
    label = 'My plugin',
    icon = 'puzzle',
    url = ('https://cfx-nui-%s/web/index.html'):format(GetCurrentResourceName()),
    permission = 'myplugin.view'
})

It takes the same fields as the table above. Without a permission, the page needs dashboard.view. To serve the page from your resource, add its files to your fxmanifest.lua:

fxmanifest.lua

files {
    'web/index.html',
    'web/**/*'
}

To remove the page yourself, call UnregisterPage with its name:

client.lua

exports['redutzu-mdt']:UnregisterPage('my-plugin')

Give officers access

A custom permission such as myplugin.view doesn’t belong to anyone yet. Add it to config/permissions.json, on the lowest grade that should see the page, in every job that should use it. The in-game permission editors only list built-in permissions, so custom ones go in the file.

config/permissions.json

{
    "police": {
        "0": ["dashboard.view", "myplugin.view"]
    },
    "sheriff": {
        "2": ["myplugin.view"]
    }
}

Here every police officer sees the page, and sheriffs see it from grade 2 up. Restart the resource, or call ReloadPermissions to apply it without a restart. See Permissions for how grades work.

​Disable pages

​Add your own pages

​From the admin panel or config

​From a resource

​Give officers access

Disable pages

Add your own pages

From the admin panel or config

From a resource

Give officers access