Crewbox docs
Crewbox is crew comms for temporary events — chat, push-to-talk voice, patch sheets, lighting plots and a network health report, all served from one small program (the box) running on a laptop at the event site. Nothing goes through the internet: phones talk to the box over the event Wi-Fi, and everything keeps working when the connection drops, because working offline is the normal case, not a fallback.
Start with whichever of these is you:
- Someone showed you a QR code. You're crew. Read Getting connected — it takes about a minute — then skim the guide for whichever module you'll live in.
- You're setting up the box for an event. Start at Running the box, then the admin panel.
What's in the app
| Module | What it does |
|---|---|
| Chat | Channels, direct messages, file sharing, mentions and alerts — always on. |
| Voice | A push-to-talk intercom in any channel, running on the box itself. |
| Patch sheets | The festival master patch as a live grid every device can edit — with the stage patch derived from it, the lineup, and changeovers. |
| Lighting | Plots with fixtures, addressing, truss estimates, Plan/Front/3D drawings — and live DMX from the rig when the box is listening. |
| Network | A continuous audit of the networks the box can see, graded for A/V use, with a report you can hand to venue IT. |
The box's admin chooses which modules are on; chat is always there.
How these docs are arranged
Every page starts with a plain summary, then goes deeper, and ends with step-by-step tasks. If you're hunting for something specific, use the search box above — it looks through every page — or try the glossary if a word is being used in a way you don't expect, which happens a lot when lighting, sound and chat all say "channel".