Events, collections, participation, and modules
Events are the shows Nexus supports. Collections group related events, such as a series, venue season, or multi-day programme.


Create an event
Create an event from Configure > Events & Collections.
Add:
- name;
- owner organisation;
- collection, if the event belongs to one;
- start and end date;
- location;
- description.
Nexus deliberately keeps the event form focused on event facts. Module setup, participation, access, and maps are separate steps so each decision has a clear owner.


Use collections
Use a collection when multiple events share a useful setup story. For example, a repeating venue programme or a multi-day event can share a collection while each event keeps its own dates and live record.
Avoid using collections as a dumping ground. If two shows do not share people, maps, templates, or reporting, they probably do not need the same collection.
Add participation
Participation records which organisations are involved in the event. Add participating organisations before assigning module roles to their people.
Create participation before access. It makes the access screens easier to read and helps prevent roles being assigned to organisations that are not actually part of the show.
Enable modules
Modules control whether a tool is available for the event. Current visible module setup includes Event Control, Mapping, and Documents where the backend has the module registered.
Use module status as a clear go/no-go decision:
- Enable Event Control when the event will use live logging.
- Enable Mapping when the event has a map or needs log locations.
- Enable Documents when show files should be shared in Nexus.
Module configuration is visible in the UI, but the full guided setup experience is still being developed. The current screen records module status; it does not yet walk a setup user through every module-specific checklist.