The Hierarchy of Control
SafetyHQ employs a robust Role-Based Access Control (RBAC) system designed to balance operational efficiency with strict security. Access isn't linear; it expands exponentially as workers move from passive participants to system architects.
The chart represents the total count of distinct "Access Granted" permission points across all 16 system modules. It reveals a stark contrast: Attendees operate with minimal visibility, while Platform Admins hold the keys to the entire kingdom.
Key Takeaway
A Platform Admin possesses nearly 8x the access capabilities of a standard Attendee.
Understanding the Ecosystem
While SafetyHQ allows for granular customization, we've found that the vast majority of operational workflows are perfectly covered by our four core pillars. Your Deployment Trainer can certainly help you craft a bespoke role if absolutely necessary, but we advise proceeding with caution.
Custom roles can sometimes create "cascading effects"—where granting one permission inadvertently opens access to linked data you meant to keep private. We strongly recommend testing any custom role in a live environment to verify visibility before rolling it out to your team.
The Attendee
"The Named Entity"
Think of the Attendee not necessarily as a software user, but as a person who needs to be accounted for. Often, they never log in at all. They exist in the system primarily so that others can document their attendance at a Toolbox Talk or log a certification against their name. If they do log in, their view is strictly passive—they can see basic safety data relevant to them, but they cannot touch, break, or change operational records.
General User
"The Boots on the Ground"
This is your standard field worker or foreman. They are the engine of your safety data. They can generate Forms, submit Incident Reports, and request SDSs. Crucially, they have "Create" power but almost no "Destructive" power. They can build the house, but they can't bulldoze it. They can see their own work and their division's work to stay informed, but the system protects them from being overwhelmed by company-wide administrative data.
Manager / Supervisor
"The Overseer"
This role bridges the gap between field ops and office admin with near-total visibility. They can see what everyone is doing, run reports across divisions, and manage the flow of information. However, SafetyHQ protects the audit trail: Managers generally cannot delete Forms, Incidents, or Corrective Actions. Their destructive power is strictly limited to asset management, such as Equipment and Documents.
Platform Admin
"The Architect"
This role holds the keys to the castle. Beyond just seeing and doing everything the Manager can do, the Admin controls the rules of the game. They decide who gets into the system (Workers), how the system behaves (Settings), and how data flows (Integrations). This role should be reserved for a select few who understand the full implications of a system-wide setting change. If the Manager runs the machine, the Admin builds it.
The Shape of Responsibility
By mapping permissions against five core functional areas, we can visualize the distinct "shape" of each worker type's capabilities.
● Attendee
Passive Access. Minimal footprint, focused solely on basic compliance viewing (SDS, Lessons) if active at all.
● General User
Operational Focus. High capability in Safety Ops (Forms, Incidents) but flat in Admin functions.
● Manager / Supervisor
High Visibility. Matches Admin in operational areas but lacks the final tier of system configuration.
Read vs. Write vs. Delete
Access isn't just about seeing data; it's about what you can do with it. This breakdown segregates permissions into three tiers of power:
- 1 View / Read: Passive access. Dominates the Attendee role.
- 2 Create / Edit: Active contribution. The core function of the General User.
- 3 Delete / Admin: Highly restricted. Managers can only delete Equipment/Docs. Admins have full control.
Notice how the "Delete" bar (Red) is non-existent for General Users and very small for Managers (Equipment/Docs only), preserving the safety data audit trail.
The "Settings" Fortress
The Settings module represents the brain of SafetyHQ. It controls integrations, user permissions, and offline modes. Access here is not shared—it is almost exclusively held by the Platform Admin.
*Visualizing the proportion of available "Settings" sub-permissions held by each role.
Detailed Permission Matrix
Full comparison of capabilities across all system roles.