Roles Definition

🔐 Roles Definition

This page describes the different user roles available in StateForce and their responsibilities. Roles are designed to support a hierarchical structure commonly used in emergency operations centers, ensuring secure and efficient access to system functionality.

---

👥 Available Roles

1. Administrator

• Has full access to all features and settings across the system.
• Can manage users, roles, permissions, and system-wide configurations.
• Can access audit logs and system metrics for compliance and maintenance.
• Manages global system configuration and institutions profiles.
• Has access to audit logs and activity tracking.

2. Operator

• Focused on field and real-time operations.
• Can create and update emergency incidents, assign resources (e.g. ambulances, fire brigades), and change statuses.
• Has access to resource dashboards, track resources locations, and manage on-duty personnel.
• Cannot modify system configuration or manage users.

3. Supervisor

• Oversees operator activity and ensures effective resource distribution.
• Can monitor incidents, access live updates, and generate operational and historical reports.
• Has visibility into system usage and incident statistics.
• Cannot modify user data, configurations, or assign roles.
• May approve or reject resource reassignments.

4. Guest

• Has read-only access to selected public dashboards or shared reports.
• Intended for external auditors, temporary users, or partner institutions with limited access needs.
• Cannot interact with or modify any operational data.

---

📊 Role Matrix Overview

Action/Permission	Administrator	Operator	Supervisor	Guest
Manage users and roles	✓
Configure system settings	✓
View incident reports	✓	✓	✓	✓
Create or update incidents	✓	✓
Assign emergency resources	✓	✓
Monitor real-time operations	✓	✓	✓	✓
Access live geospatial data	✓	✓	✓	✓
Generate statistics/reports	✓		✓
View activity logs	✓		✓
Access read-only dashboards	✓	✓	✓	✓

---

📌 Additional Notes

• Roles can be customized per agency in future versions.
• Role permissions follow the principle of least privilege, ensuring minimal necessary access.
• When assigning roles, always validate the operational scope and clearance level of the user.

---

For suggestions or changes to role definitions, please contact a system administrator or the project lead.