The admin panel

The cog in the sidebar's identity row opens the admin panel. Everyone can see the cog — a hidden control is how a box loses its admin — but it opens with the admin password, which is not the event PIN and not anyone's personal PIN (the three codes).

The unlock lives in memory only: closing the app re-locks it, and the Lock button does it on the spot — use it before handing your phone to someone.

Crew

Every account on the box, with presence and role. The one action you'll actually use mid-event is Reset PIN — for the crew member who invented a PIN at 9am and lost it by noon. Type a new one, tell them, done.

Channels

Rename a channel, fix its topic, or Retire it (two-step confirm) when a stage wraps. #general can't be retired — there's always somewhere everyone is.

This box

The health of the machine you're running on, as a readiness list — crew network, voice, modules, install/offline support, the Android app download, disk space — each row with a plain verdict and, when it isn't fine, the fix.

Two rows exist to warn you before something takes the box down rather than after:

• Power — whether this machine is on mains, and if not, how long it has left. A laptop nobody plugged in is the commonest crewbox, and it fails with no warning at all: fine, then gone, discovered by crew phones sitting on "Connecting" mid-set. It goes amber on battery and red under half an hour. Machines with no battery don't show the row.
• Backup — how long since deploy/backup.sh last finished, and where it wrote to. The box can't go looking for backups (they're on a USB stick that usually isn't plugged in), so the script leaves it a note. A backup regime that quietly stopped three events ago looks identical from the production desk to one that ran last night; this is the row that tells them apart.

Below the list, the settings:

• Event name, Event PIN, Wi-Fi network — the setup-page answers, editable live. Changing the PIN notes that the poster and /connect need re-checking.
• Networks — the crew-side adapter, lighting-network listening (off / sACN / Art-Net / both) and its adapter, and the sACN universes. Join links update immediately; socket changes apply when the box restarts, and a banner reminds you while saved settings differ from what the box started with. There's no restart button — stop and start the box (how).
• Admin password — changeable here; doing so locks every other device that had the panel open.

Settings pinned by environment variables show a note instead of a field — the environment always outranks the panel, which is also the recovery path.

This network

What the venue's network is actually providing, probed on demand (Check again): the box's address, internet (a captive portal is flagged; plain "no internet" is just information — the box doesn't need it), whether crew can reach the box by its name, certificate expiry, and clock sanity.

When the name check fails, a Download DNS config button appears with a ready-made crewbox-dns.conf for the venue router — hand it to whoever runs the router instead of explaining DNS at the production desk.

That file carries a second, clearly-marked optional block: the addresses phones fetch to decide whether a network has internet. Adding it stops iPhones abandoning the crew Wi-Fi for mobile data — see the "no internet" problem for what that failure looks like and why it's worth doing.

Export

Download chat logs — every user, channel and message as one JSON file for the post-event archive. Patch sheets and plots export from their own modules as CSV.