Module configuration
Module status decides which tools are available for an event. Nexus evaluates module status separately from user access: the module must permit the operation and the user must still have the relevant role.
Open an event in Configure, then choose Modules. The registered modules currently include Event Control, Mapping, and Documents.
The current module configuration UI is not yet a full guided setup centre. It does not walk a user through all module-specific prerequisites, health checks, or publishing steps. Track this in Feature notes.
How to use it now
Choose one lifecycle state:
- Active allows permitted users to read and change module data.
- Read only keeps permitted views and exports available but blocks operational changes.
- Disabled removes ordinary module routes and API access for the event.
Enter a reason for every lifecycle change. Nexus records the reason and guards against saving over a newer change made by another administrator.
An event override takes precedence over its collection and the module default. Choose Use inherited state while editing an override to remove it and resume the nearest collection or module-default policy. This also requires a reason; it does not delete any module-owned data.
Changing state does not delete module data, configuration, or assignments. Reactivating a module exposes the retained records again. During a live change, connected clients refresh their module context. A user on a newly disabled page is moved to another available page and any supported unsent draft is retained.
An event also becomes read-only automatically after its end date. This event-level rule downgrades active modules to read-only without changing their saved activation configuration. An event administrator can temporarily enable Allow writes after this event ends in Event details when historic records must be corrected.
A collection-level module or access change cannot be saved when it would alter a historic descendant event that is still read-only. Enable historic writes on the affected event only for the duration of the controlled configuration change.
When a module has live work in progress, move it from Active to Read only first. Confirm operators have finished or saved their work before changing it to Disabled.
What to check after enabling a module
- The module appears for users with the right access.
- A read-only user can view existing data but cannot see or use write controls.
- A disabled module is absent from Show navigation and direct access is rejected.
- Event Control has usable settings and categories.
- Mapping has a configured base map and any required layers.
- Documents has the right editor and viewer access.
Do not activate every module by default. Activate the tools the show will actually use, then rehearse those tools with the users who will operate them.