Skip to main content

Nexus user manual

Nexus is for the people who run a show when the gates are open, the radio is busy, and every decision needs a clear trail.

This manual has two paths:

Show users Use Nexus during a live event: log incidents, view the map, open documents, and export the control record.

Configure Set the event up: create the show, invite people, switch modules on, prepare maps, and tune Event Control.

The screenshots are generated from the real Nexus app with the local e2e seed data. They are not hand-drawn. If the UI changes, the route coverage check and screenshot manifest should move with it.

Best practice

Set up the event first, then run the show from the live pages. It keeps the live shift simple: operators see only the tools they can use, and the setup decisions stay out of the control room flow.

Where to start​

  • If you are in the control room, start with Show users.
  • If you are preparing an event, start with Configure.
  • If something in the app looks available but is still being finished, check Feature notes.

What Nexus can do today​

  • Give live users a single workspace for Event Control, Mapping, Documents, and exports.
  • Keep Event Control structured enough for handover, search, and review without slowing down quick logging.
  • Let setup users build the event model: organisations, people, participation, modules, access, maps, and Event Control settings.
  • Keep an audit stream so configuration changes are traceable.
  • Generate documentation screenshots across desktop and mobile from the same seeded product state used by browser tests.

The opinionated setup order​

Nexus works best when setup follows this order:

  1. Create or confirm the organisations.
  2. Create the event or event collection.
  3. Add participating organisations.
  4. Enable the modules the show will use.
  5. Assign access through role bundles first, then direct module roles only where needed.
  6. Apply the standard Event Control template, then adjust local categories, agencies, and mappings.
  7. Configure maps, imports, and layers.
  8. Run a short rehearsal in the Show pages before the event starts.

That order avoids the awkward parts: people invited before their organisation exists, live pages opened before modules are enabled, and operators trying to log against categories that have not been agreed.