Modules Reference

Nexalix is built around a modular architecture. Beyond the core incident management features — creating, tracking, and resolving incidents — optional modules extend the platform with specialised capabilities. Each module can be enabled or disabled per organisation depending on your plan and operational needs.

Available modules

Module	Feature key	Description
SLA Management	`sla_timers`	Set time-based resolution targets and track compliance.
Asset Registry	`asset_registry`	Catalogue physical infrastructure and link incidents to assets.
Cost Tracking	`cost_tracking`	Record and analyse costs associated with incident resolution.
Citizen Reporting	`citizen_reporting`	Public portal for citizens to submit and track reports.
Auto-Assignment	`auto_assignment`	Automatically route incidents to the right team member.
KML Layers	`kml_layers`	Upload geographic overlays for infrastructure visualisation.

Enabling modules

Modules are enabled in two ways:

Plan-based — Your subscription plan includes a set of modules by default. When your organisation is created, the modules included in your plan are activated automatically.
Administrator override — Organisation administrators (and super administrators) can enable or disable individual modules from the Admin panel, under Organisation Settings > Features.

SLA Management

Set time-based targets for incident resolution and receive automated notifications when deadlines approach or are missed.

Key features:

Create rules based on incident template, priority field, and deadline (in hours).
Configurable warning threshold (percentage of deadline elapsed before warning).
Automatic email and push notifications for warnings and breaches.
Compliance dashboard with overall rate, breakdown by template, and trend charts.

Permissions: sla.view (view rules and compliance), sla.manage (create, edit, delete rules).

For a detailed setup guide, see SLA Configuration.

Asset Registry

Maintain a catalogue of physical assets (pipes, meters, valves, streetlights, vehicles) and link them to incidents for better tracking and root-cause analysis.

Key features:

Create assets with name, location (GPS), code, type, and custom metadata.
Define asset types with structured metadata schemas (e.g., “Diameter”, “Material”, “Installation Date”).
Auto-generated asset codes based on type prefix (e.g., PUMP-001, VALVE-042).
Link incidents to assets during creation or editing.
View all incidents associated with a specific asset.
Nearby asset search — find assets close to an incident’s location.

Permissions: assets.view (view assets), assets.manage (create, edit, delete assets and types).

Cost Tracking

Record labour, materials, and equipment costs for each incident. Generate summary reports to understand where your operational budget is being spent.

Key features:

Record cost entries per incident with amount, category, and description.
Pre-defined cost categories (labour, materials, equipment, external) with the option to create custom categories.
Summary reports: total costs by category, by template, and by top incidents.
Trend analysis to compare costs across time periods.
Export cost data for external reporting.
Organisation-level currency setting.

Permissions: costs.view (view costs and reports), costs.record (add cost entries), costs.manage (full management including deletion).

Citizen Reporting

Allow members of the public to report incidents through a branded web portal without needing a Nexalix account.

Key features:

Public reporting form with location, description, and photo upload.
Unique reference codes for citizens to track report status.
Moderation workflow: approve (creates incident), reject, or merge with existing incident.
CAPTCHA protection, rate limiting, and geographic bounds validation.
Duplicate detection based on location proximity.

Permissions: citizen_reports.view (view reports), citizen_reports.moderate (approve, reject, merge), citizen_reports.delete (delete reports).

For a detailed setup guide, see Citizen Portal.

Auto-Assignment

Automatically route new incidents to the right team member based on geographic zones, incident type, and team schedules.

Key features:

Create assignment pools with members, template associations, and geographic zones.
Draw zones on the map to define each pool’s geographic coverage.
Configure rotation schedules for shift-based operations.
Assignment logs showing full routing history.
Activate/deactivate pools without deleting them.

Permissions: auto_assignment.view (view pools and logs), auto_assignment.manage (create, edit, delete pools).

For a detailed setup guide, see Auto-Assignment Rules.

KML Layers

Upload KML files to display geographic overlays on the incidents map — infrastructure networks, service zones, administrative boundaries, or any other geographic data.

Key features:

Upload .kml or .xml files (up to 10 MB per file).
Set a custom name and colour for each layer.
Toggle layer visibility on the map.
Layers are displayed beneath incident markers for clear visual context.
Layer count is governed by your organisation’s quota.

Permissions: kml_layers.manage (upload, edit, delete layers). All authenticated users can view layers on the map.

Module availability by plan

The modules available to your organisation depend on your subscription plan. Contact your Nexalix administrator or check the pricing page for details on which modules are included in each plan tier.

If a module is not available on your current plan, the corresponding sidebar item and features will not appear in the interface.