Admin Panel & Permissions

The Admin Panel

The Admin Panel is where you run your helicopters from inside the game. It gives you a live list of every helicopter on the server — with teleport, repair, refuel and delete — plus a live map of where they all are, editors for every setting on this site, server-wide tools, saved loadouts, statistics, a log reader, and the staff list itself. Anything you change in the panel takes effect at once, with no restart.

Open it with F10 (rebindable — DayZ Options → Controls → CZ Autoz Helicopter group)
It only opens for players on your admin list. For everyone else the key does nothing at all
Everything an admin does in the panel is written to the activity log, with their name and Steam ID

Becoming the First Owner

Admins live in their own file, next to mod_config.json in your server profile:

$profile:\CZAutoz_Heli\permissions_admins_config.json

The file is created the first time the server starts, with a placeholder entry in it. Replace the placeholder with your own SteamID64 and restart:

{
  "whitelistRetryMinutes": 15,
  "entries": [
    { "steamID64": "76561198012345678", "role": "owner" }
  ],
  "roles": [
    { "name": "owner", "permissions": ["all"] },
    { "name": "admin", "permissions": ["mod.config.view", "heli.config.view", "heli.list.view", "heli.list.teleport", "heli.list.repair", "heli.list.refuel", "heli.list.delete", "tools.spawn", "stats.view", "presets.view", "presets.spawn", "presets.save", "presets.delete", "log.view"] }
  ]
}

Field	What it is
`entries`	Your admins. Each one is a `steamID64` and the `role` they hold, and nothing else — what an admin can do comes entirely from their role
`roles`	The roles themselves — each is a `name` and the list of permissions it grants
`whitelistRetryMinutes`	How many minutes the server waits before trying the whitelist check again after a failed one. Nothing to do with admins — it just happens to live in this file. Kept between 5 and 60

The placeholder ID (7656119XXXXXXXXXX) is ignored and never gives anyone access. You can find your own SteamID64 on steamid.io or in your Steam profile address.

Once you have one owner, everything else — adding staff and building roles — is done in-game from the panel’s Admins tab. The file is just where the panel saves it all. Editing the file by hand and restarting always works too.

How Access Works

There are three questions, and the server asks all three before it lets an admin do anything:

Are you on the list? Your SteamID64 has to be in entries, or the panel will not open at all
Which role do you hold? Your entry names exactly one
What does that role allow? Its list of permissions decides what you can see and what you can do

The built-in owner role holds the special permission all, so it passes every check. Every other role has exactly the permissions you give it:

Tabs disappear if you cannot view them — an admin without stats.view simply has no Statistics tab
Buttons stay on screen. Pressing one you are not allowed to use brings up a “Permission Declined” message naming exactly what you are missing, so your staff know precisely what to ask you for
The Admins tab is visible to every admin, as a list they can read but not change. The add, edit and remove buttons only appear for someone holding admins.manage
The Settings tab — colour theme, panel size and a readout of your own role — is always available
The Our Mods and Cars tabs are just information and have no permission attached — see below

Built-in Roles

Role	Permissions	Notes
`owner`	`all` — everything, always	Cannot be deleted or changed. Only an owner can make somebody else an owner. It never appears in the roles list, because it sits above the whole system
`admin`	Every tab that can be viewed, all four helicopter actions (teleport, repair, refuel and delete), spawning by classname or from a saved loadout, managing loadouts, and reading the logs	The standard staff role, and the one anybody falls back to. It cannot be deleted, but you are free to change what it grants

The default admin role deliberately leaves out seven permissions: mod.config.edit and heli.config.edit (changing your settings), tools.reload, tools.repair_all, tools.refuel_all and tools.delete_empty (jobs that hit every helicopter at once), and admins.manage (changing the staff list). A default admin can look after the aircraft day to day, but cannot retune your server or promote themselves.

Every Permission Key

Key	Unlocks	In default `admin`?
`all`	Everything in this table, and anything added in future releases	—
`heli.list.view`	The Helicopters tab — the live list of every helicopter, with where it is, who is in it and what state it is in	✅
`heli.list.teleport`	Teleport to the selected helicopter	✅
`heli.list.repair`	Repair the selected helicopter	✅
`heli.list.refuel`	Refuel the selected helicopter	✅
`heli.list.delete`	Delete the selected helicopter	✅
`mod.config.view`	The Mod Config tab — read every server-wide setting	✅
`mod.config.edit`	Change and save the server-wide settings. Takes effect at once	—
`heli.config.view`	The Heli Config tab — read the settings for each individual helicopter	✅
`heli.config.edit`	Change, save or reset a helicopter’s own settings. Takes effect at once	—
`tools.spawn`	Spawn a helicopter by classname	✅
`tools.reload`	Re-read every settings file from disk	—
`tools.repair_all`	Repair every helicopter on the server at once	—
`tools.refuel_all`	Refuel every helicopter on the server at once	—
`tools.delete_empty`	Delete every helicopter that nobody is sitting in	—
`stats.view`	The Statistics tab — how many helicopters there are, their fuel and condition, and the server frame rate	✅
`presets.view`	The Presets tab — the saved helicopter loadouts	✅
`presets.spawn`	Spawn a helicopter from a saved loadout	✅
`presets.save`	Save a new loadout	✅
`presets.delete`	Delete a saved loadout	✅
`log.view`	The Logs tab — all six views: Activity, Debug, Physics, Whitelist (shared across all CZ Autoz products), Script Log and Server RPT	✅
`admins.manage`	Add and remove admins, change their roles, and create or delete roles	—

The Tools tab shows up if you hold any one of the five tools. permissions. Each button inside still checks its own permission separately, so a role with only tools.spawn sees the tab but cannot press the others.

The Helicopters tab also has a live map next to the list. Every helicopter on the server is shown on it as it moves, and picking one from the list marks it on the map. You can drag the map around, and it only appears while that tab is open.

The Two Tabs With No Permission Key

Two tabs are there purely to tell you what is installed. Neither has a permission attached, so every admin sees them whatever their role.

Tab	When it appears	What it shows
Our Mods	Always	A summary of the CZ Autoz range — what this mod includes, along with the version your server is running, and what the vehicle range covers. Nothing here can be changed and nothing here affects your server
Cars	Only when CZ Autoz car mods are found on the server	A list of the CZ Autoz vehicle mods it found, grouped into tiers, packs and single vehicles. With no car mods installed the tab is hidden completely

Creating a Staff Role

From the Admins tab (needs admins.manage), in the Roles box:

Type a role name in lower case, for example moderator
Type the permissions from the table above, separated by commas
Press Add. The role exists straight away and shows up in the role pickers

A sensible moderator role, for example:

heli.list.view, heli.list.teleport, heli.list.repair, heli.list.refuel, stats.view, log.view

They can keep an eye on the helicopters, teleport to any of them, patch one up, refuel it and read the logs — but they cannot delete an aircraft, spawn one, change a single setting, or touch the staff list.

To edit a role, add it again under the same name with the new list of permissions. The old list is replaced, and everyone holding that role sees their panel update straight away
Typos cannot hide. Anything that is not a real permission is thrown out when the role is saved, and named in the server log (dropped unknown permission key(s): heli.list.veiw). A misspelt permission can never sit in a role looking as though it grants something
Deleting a role moves everybody who held it onto the built-in admin role

Managing Admins

In the Admins tab (needs admins.manage):

Add — type a SteamID64 (digits only) and pick a role, or choose a player who is online right now from the drop-down and add them straight away
Edit — the ✎ button on a row lets you change that admin’s role
Remove — the button on that admin’s row

Every change takes effect immediately. Somebody you just added can press F10 seconds later without rejoining, a removed admin has their open panel closed for them, and a role change updates their tabs on the spot.

The Safety Rails

All of this is enforced by the server itself, so a player running a modified game cannot get round it:

Only an owner can make another owner, change an existing owner, or remove one
The last owner cannot be touched. The panel refuses to remove or demote the final owner, so you can never lock yourself out. The only way to end up with no owners at all is to edit the file yourself
Nobody can change or remove their own entry through the panel. It takes a second admin, or an edit to the file. That stops anyone promoting themselves
admins.manage is not the same as all. Somebody who is not an owner cannot create a role holding all or admins.manage, so they can never build a role more powerful than their own and hand it out
owner and admin can never be deleted, so there is always a role to fall back on
Everything is recorded. Every addition, edit, removal and refused attempt is written to the activity log under the ADMIN_ labels

Locked yourself out anyway? Open permissions_admins_config.json, add yourself back with "role": "owner" and restart. The file always wins.

Getting Started

The Fleet

Features

Server Configuration

More

Admin Panel & Permissions

The Admin Panel

Becoming the First Owner

How Access Works

Built-in Roles

Every Permission Key

The Two Tabs With No Permission Key

Creating a Staff Role

Managing Admins

The Safety Rails

​The Admin Panel

​Becoming the First Owner

​How Access Works

​Built-in Roles

​Every Permission Key

​The Two Tabs With No Permission Key

​Creating a Staff Role

​Managing Admins

​The Safety Rails

The Admin Panel

Becoming the First Owner

How Access Works

Built-in Roles

Every Permission Key

The Two Tabs With No Permission Key

Creating a Staff Role

Managing Admins

The Safety Rails