Admin: System

The System tab provides access to system-wide configuration, user account management, third-party integrations, and the audit log. Changes made here affect the entire installation.

Navigate to Admin > System.

The System tab contains four sub-tabs:

Sub-tab	What you manage
Settings	Alert configuration and audit retention
Integrations	Emergency notification services
Users	Login accounts for system operators
Audit Log	Full record of system changes with filtering and export

---

Settings

The Settings sub-tab has two sections accessed via its own inner tabs: Alerts and Audit.

Alert Settings

Alert settings control which notification channels are active and what system events trigger alerts.

Screenshot placeholder: [Alert settings form with channel toggles and event checkboxes]

Notification Channels

Toggle	Default	Description
Email Notifications	On	Send alert notifications via email
SMS Notifications	Off	Send alert notifications via SMS (requires SMS provider in Integrations)
Push Notifications	On	Send in-app push notifications

When Email Notifications is enabled, two additional fields appear:

• From Email Address — the sender address for system emails (e.g. mustering@yourorg.com)
• From Name — the display name for outbound emails (e.g. NISC Mustering System)

Event Triggers

Toggle	Default	Triggers when
Low Battery Alert	On	A beacon battery drops below the low threshold (configured in BLE Settings)
Critical Battery Alert	On	A beacon battery drops below the critical threshold
Device Offline Alert	On	A tracked beacon stops reporting
Gateway Offline Alert	On	A gateway receiver stops reporting
Emergency Alert	On	A muster event is triggered

Alert Cooldown

Alert Cooldown (minutes) — the minimum time between repeated alerts for the same event. Default: 5 minutes. This prevents a flapping device from generating hundreds of notifications. Set to 0 to disable cooldown (not recommended in production).

Saving Alert Settings

Click Save Changes in the Alerts section. Changes apply immediately to all subsequent alert events.

---

Audit Retention Settings

The Audit retention setting controls how long the system keeps audit log entries in the database.

Setting	Default	Description
Retention Period (days)	90	Audit log entries older than this many days are automatically purged by the scheduled cleanup job

To change the retention period:

1. Adjust the number in the Retention Period field.
2. Click Save Retention.

Note: Reducing the retention period will cause older audit entries to be deleted at the next cleanup cycle. Increasing it has no immediate effect — historical entries that were already deleted cannot be recovered. If you need a longer audit trail for compliance, increase this value before the original entries age out.

Tip: 90 days is suitable for most operational use cases. Compliance-heavy environments (e.g. OSHA recordkeeping requirements) may require 365 days or more. Consult your compliance officer before changing this value.

---

Users

Users are the accounts that can log in to the NISC Mustering System. Each user has an email address, a display name, a role, and an active/locked status.

Screenshot placeholder: [Users table showing display name, email, role badge, status, last login, and action buttons]

Viewing Users

The Users list shows:

Column	Description
User	Avatar initials, display name, and email address
Role	Badge showing the assigned role (Admin / Safety / Operator / Viewer)
Status	Active (green) or Inactive (grey)
Last Login	Date and time of the most recent successful login
Failed Logins	Count of consecutive failed login attempts (3 or more locks the account)
Actions	Edit, Reset Password, Unlock, Delete buttons

You can filter the list by typing in the search bar (matches name, email, or role) and by using the Role and Status dropdowns.

Creating a User

1. Click the Add User button in the top-right area of the Users section.
2. In the dialog that opens, complete the required fields:
   • Display Name (required) — the name shown throughout the system
   • Email Address (required) — used for login; must be a valid email format
   • Role (required) — select from the available roles (see Roles and Permissions)
   • Active — toggle on to allow the account to log in immediately
3. Under Password, choose one of:
   • Generate Password (default) — the system creates a secure temporary password and displays it once after saving.
   • Set Password — type a custom password of at least 8 characters.
4. Click Add User.
5. If a temporary password was generated, a credential dialog appears showing the username, email, and password. Copy or note this password — it is only shown once. Click Copy to Clipboard if available.

Important: Share the temporary password securely with the new user. They should change it on first login.

Editing a User

1. Find the user in the list and click the pencil (Edit) icon in the Actions column.
2. Update any of the following fields:
   • Display Name
   • Role
   • Active status
3. Email address cannot be changed after account creation.
4. Click Save Changes.

Note: You cannot set a new password from the Edit dialog. Use the Force Password Reset action instead.

Forcing a Password Reset

When you force a password reset, the system generates a new temporary password and the user must change it on next login.

1. In the Users list, click the Reset Password icon (key icon) next to the user.
2. A confirmation dialog asks you to confirm.
3. Click Reset Password to proceed.
4. The credential dialog displays the new temporary password. Copy it and share it securely with the user.

Unlocking a Locked Account

An account is automatically locked after 3 or more consecutive failed login attempts.

1. In the Users list, locked accounts show a padlock icon and a failed-login count.
2. Click the Unlock icon next to the locked account.
3. Confirm the action in the dialog.
4. The failed login counter resets and the account can log in again.

Deactivating or Deleting a User

Deactivate (preferred for temporary suspension):

1. Open the Edit dialog for the user.
2. Toggle Active to off.
3. Save Changes. The user cannot log in but the account and its history are retained.

Delete (permanent):

1. Click the Delete (trash) icon in the Actions column.
2. Confirm in the dialog.
3. The account is permanently removed. This action cannot be undone.

Warning: Deleting a user removes their login account but does not remove any personnel records associated with them. If the user is also tracked as personnel, the personnel record must be deleted separately.

Exporting Users

Click the Export button above the table to download a CSV file of the currently filtered user list. The export includes display name, email, role, status, failed login count, and last login timestamp.

---

Integrations

The Integrations sub-tab manages connections to external notification services used during muster events and alerts.

Emergency Services

The Emergency Services configuration panel allows you to set up the SMS, voice, and email providers that deliver notifications when a muster event is initiated.

Screenshot placeholder: [Emergency Services config panel with provider selection and credential fields]

Configuration options for each channel depend on the selected provider. Common providers include:

• SMS — Twilio, Azure Communication Services, or similar SMS gateway
• Voice calls — Twilio or Azure Communication Services
• Email — SMTP relay or Azure Communication Services email

For each enabled channel:

1. Select the provider from the dropdown.
2. Enter the required credentials (API key, account SID, sender number/address, etc.).
3. Use the Test button (if available) to send a test message and confirm the integration is working.
4. Click Save.

Important: Credentials entered here are stored encrypted in the system. Do not share raw API keys with other users. Rotate credentials in the provider dashboard and update them here if a key is compromised.

Note: The Integrations section is expandable. Future versions of the system will add webhook support and additional provider options here.

---

Audit Log

The Audit Log records every significant action taken in the system: user logins, configuration changes, personnel record modifications, muster events, alert sends, and more. It is the definitive record of who did what and when.

Screenshot placeholder: [Audit Log table with timestamp, user, action, resource, status, and expandable detail rows]

Statistics Summary

Four summary cards at the top of the Audit Log show activity for the last 24 hours:

Card	Description
Total Actions	Total number of logged events in the last 24 hours
Successful	Events that completed without error
Errors	Events that resulted in a failure
Active Users	Number of distinct users who performed actions

Understanding Audit Log Entries

Each row in the audit log represents a single recorded action:

Column	Description
Timestamp	Date and time the action occurred
User	The logged-in user who performed the action
Action	The type of action (e.g. Create, Update, Delete, Login, Send SMS)
Resource	The type of object that was affected (e.g. Personnel, Building, User, Settings)
Resource ID	The identifier of the specific record affected
Status	Success or Error
Summary	A human-readable description of the action

Click on any row to expand it and see the full detail payload — for example, the before/after values when a record was updated, or the error message when an action failed.

Common Action Types

Action	What it records
create	A new record was created
update	An existing record was modified
delete	A record was deleted
login_success	A user logged in successfully
login_failed	A login attempt failed
login_blocked	A login was blocked due to account lockout
logout	A user logged out
password_changed	A user changed their own password
password_reset	An admin reset a user's password
settings_update	System settings were changed
send_sms	An SMS notification was sent
send_email	An email notification was sent
send_voice	A voice call notification was initiated
circuit_breaker	A notification circuit breaker was opened or reset
toggle	A record's enabled/disabled state was changed
trigger	A muster event or alarm was triggered

Filtering the Audit Log

Use the filter bar above the table to narrow results:

Text search — type any keyword to search across user names, action types, resource types, and detail content.

Date range — click the date picker to select a custom range. Use the quick presets for convenience:

• Today — from midnight to now
• Last 7 days
• Last 30 days

Action filter — narrow to a specific action type (e.g. show only Delete actions).

Resource filter — narrow to a specific resource type (e.g. show only changes to Buildings).

Status filter — show only successful actions, only errors, or all.

Source filter — toggle between User actions (default, human-initiated actions) and All (includes system-generated entries such as scheduled jobs and background processes).

Multiple filters can be active simultaneously. Click Clear Filters to reset all filters at once. The filter bar highlights in amber when active filters are in place.

Paginating Results

The audit log is paginated. Use the page controls at the bottom of the table to navigate. You can adjust the number of rows shown per page (25, 50, or 100 entries).

Viewing Action Details

1. Click on any audit log row to expand it.
2. The expanded row shows a detailed summary: for example, Updated Personnel 123 — changed department from Engineering to Operations.
3. For more technical detail (raw JSON payload), the expanded view shows the full details field if it contains structured data.

Exporting the Audit Log

Note: Direct CSV export from the Audit Log view is not currently available in the UI. For compliance export requirements, contact your system administrator to request a database-level export of the audit_logs table. This is accessible to administrators with direct database access.

Audit Log and Data Retention

Audit log entries are automatically purged based on the Retention Period configured in Settings > Audit (see above). Once entries are deleted they cannot be recovered from the application. If long-term retention is required for legal or regulatory reasons, set up a separate archival process (e.g. Azure Log Analytics or blob storage archiving) in coordination with your IT team.