Organisation Settings

Organisation settings control how your Nexalix workspace operates — from incident workflows and departments to branding and security. Only Organisation Admins (or Super Admins) can access these settings.

Departments (Sub-organisations)

Departments divide your organisation into teams or areas of responsibility. Incidents can be assigned to a department, and templates can be restricted to specific departments.

Managing departments

1. Go to Admin → Organisation → Departments.
2. To create a department, click Create and enter a name.
3. To rename or delete a department, use the actions menu on each row.

Note

A department cannot be deleted if it has users or incidents assigned to it. Reassign them first.

Assigning users to departments

Each user has a primary department set in their profile. When creating or editing a user, select their department from the dropdown.

Incident statuses and workflows

Nexalix uses a configurable status workflow for incidents. Each organisation defines its own set of statuses and the allowed transitions between them.

Default statuses

The statuses available depend on your organisation’s vertical (sector):

• Nexalix (generic): Open → In Progress → Resolved
• Water: Detected → In Progress → Repaired
• Municipal: Reported → Acknowledged → Scheduled → In Progress → Completed / Rejected

Status flags

Each status has flags that control its behaviour:

Flag	Meaning
Initial	Default status for new incidents. Exactly one status should be initial.
Resolved	Marks the incident as fixed. Triggers SLA resolution timers.
Terminal	No further transitions are possible. The incident is closed.

Managing statuses

1. Go to Admin → Incident Statuses.
2. You can create new statuses, edit labels and colours, reorder them, and define transitions.

Configuring transitions

Transitions define which status changes are allowed. For example, you might allow “Open → In Progress” but not “Resolved → Open”.

1. Click on a status to open its detail view.
2. In the Transitions section, add the statuses that this status can transition to.
3. Optionally, require a specific permission for the transition.

Tip

A well-designed workflow prevents incidents from being moved backward without intention. Use the terminal flag to lock completed incidents.

Incident templates

Templates define the structure of an incident — which custom fields appear, their types, and validation rules. See the dedicated Incident Templates guide for full details.

Branding

Organisation Admins can customise the platform’s appearance for their team:

1. Go to Admin → Organisation → Branding.
2. You can configure:

Setting	Description
Product Name	The name shown in the platform header and emails (max 50 characters).
Logo URL	URL to your organisation’s logo (HTTPS only). Displayed in the header and emails.
Primary Colour	The main brand colour used for buttons and highlights (hex format, e.g., #2563EB).
Accent Colour	Secondary colour used for links and interactive elements.

Changes take effect immediately across the web application and in all email notifications.

Two-Factor Authentication (2FA)

Organisation Admins can enforce two-factor authentication for all users in the organisation.

1. Go to Admin → Organisation → Security.
2. Toggle Require 2FA.
3. When enabled, users who have not set up 2FA will be prompted to do so on their next login. They cannot access the platform until 2FA is configured.

Individual users can always enable 2FA voluntarily from their Settings → Security page, regardless of the organisation-level setting.

Notification management

Admins can view and monitor notification activity across the organisation:

1. Go to Admin → Notifications.
2. The Summary tab shows subscription counts per notification type.
3. The Logs tab shows recent notification deliveries (email and push).

Individual notification preferences (which types of notifications to receive, and any template or department filters) are managed by each user from their Settings → Notifications page.

Quotas

Depending on your plan, your organisation has limits on certain resources (incidents per year, number of users, templates, dashboards, etc.). Current usage is visible in the admin panel and in the authentication response.

If you reach a quota limit, the platform will display a message indicating which limit was reached. To increase limits, upgrade your plan or contact your Nexalix administrator.

Modules

Nexalix offers optional modules that extend the platform’s capabilities. Available modules depend on your plan:

Module	Description
Auto-Assignment	Automatically route incidents to team members based on location, templates, and schedules.
Asset Registry	Track physical assets and link incidents to specific equipment or infrastructure.
Cost Tracking	Record and report on costs associated with incident resolution.
SLA Management	Define service-level agreements with deadlines, warnings, and compliance tracking.
KML Layers	Upload geographic data layers to overlay on the incident map.
Citizen Portal	Allow citizens to submit reports and track their status publicly.

Modules are enabled at the organisation level. Organisation Admins can see which modules are active from the admin panel.