Admin Panel & Permissions

​

The Admin Panel

• Open it with F10 (rebindable — DayZ Options → Controls → CZ Autoz Helicopter group)
• It only opens for players listed as admins; everyone else’s key does nothing
• Everything an admin does in the panel is written to the activity log with their name and Steam GUID

​

Becoming the First Owner

$profile:\CZAutoz_Heli\permissions_admins_config.json

{
  "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"] }
  ]
}

​

How Access Works

1. Are you listed? Your SteamID64 must be in entries — otherwise the panel won’t open at all
2. What role do you hold? Your entry names exactly one role
3. What does that role grant? The role’s permission keys decide what you can see and do

• Tabs hide when you lack their view key — an admin without stats.view simply has no Statistics tab
• Action buttons stay visible — clicking one you lack shows a “Permission Declined” dialog naming the exact key you’re missing, so your staff know precisely what to ask you for (since v0.3.1 — earlier builds denied silently)
• The Admins tab is visible to every admin as a read-only roster; the add/edit/remove controls only appear with admins.manage
• The Settings tab (theme, UI scale, your own role readout) is always available

​

Built-in Roles

​

Every Permission Key

​

Creating a Staff Role

1. Enter a role name — lowercase, e.g. moderator
2. Enter the permissions as comma-separated keys from the table above
3. Click Add — the role exists immediately and appears in the role dropdowns

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

• Editing a role = add it again under the same name with the new key list — the definition is replaced, and every member’s panel updates live (since v0.3.1)
• Typos can’t hide — unknown keys are dropped on save and named in the server’s script log (dropped unknown permission key(s): heli.list.veiw), so a misspelled key can never sit in a role looking like it grants something (since v0.3.1)
• Deleting a role moves everyone who held it to the built-in admin role

​

Managing Admins

• Add — enter a SteamID64 (digits only) and pick a role, or select a currently online player from the dropdown and add them directly
• Edit — the ✎ button on a row opens the role picker for that admin
• Remove — the button on their row

​

The Safety Rails

• Only an owner can create another owner, change an existing owner, or remove one
• The last owner is untouchable — the panel refuses to remove or demote the final owner, so you can never lock yourself out. Going to zero owners is only possible by editing the file
• Nobody can edit their own role through the panel — it takes a second admin (or the file). This closes the classic self-escalation loop
• admins.manage is not all — a non-owner staff manager cannot create a role carrying all or admins.manage, so they can never mint a role stronger than themselves and hand it out
• owner and admin cannot be deleted — the fallback role always exists
• Everything is audited — every add, edit, removal, denied attempt and live grant/revoke lands in the activity log under the ADMIN_* tags