Battalion Admin

The context

Battalion's Rover toolboxes are connected hardware rather than plain storage, and they open two ways: from the mobile app, or from a keypad code on the box itself. That makes access the thing actually worth managing. A box is no use to a crew that cannot open it, and rather worse than no use to a company that cannot stop a departing worker from opening it. What was missing was the surface where the relationship between a person and a box gets set.

What the work involved

• Built the admin panel in Next.js across two sections, Devices and Users, each a searchable list with edit and delete on every row.
• Made the device and the user two views onto the same relationship: opening a device lists the users connected to it, opening a user lists the devices connected to them, and access is granted or revoked from whichever side the work happens to start on.
• Built the device record, covering its name and the current keypad passcode that opens the box, so a code can be read or changed without standing in front of the unit.
• Built the user record, covering name, email, phone, and occupation, with the option to remove a user outright or block them, which cuts access across every device at once instead of one connection at a time.
• Kept the panel writing to the same device and user records the mobile app reads, so a connection revoked here is refused the next time that phone tries to connect.

Outcome

Access stopped being a property of the physical box and became something editable. A new crew member gets connected to the boxes they need, and someone leaving is blocked once rather than unpaired device by device.