Units
Units are the organizational groupings within your space. They represent the logical divisions of your company: offices, departments, sites, teams.
Some concrete examples:
- Head Office — the main office with administrative and technical staff
- Production Department — operational area with machinery and production staff
- Warehouse — storage area with equipment and chemical substances
- North Site — a temporary site with dedicated work teams
What they’re for
Section titled “What they’re for”Units are the central mechanism that links resources to actions. Without units, there would be no way to determine which requirements apply to which resources.
The principle is simple: by assigning resources and actions to the same unit, you define which requirements apply to which resources. From this intersection, compliance obligations are generated automatically — there is no need to create them manually.
For example, if you assign the employee “John Smith” and the action “Fire safety training” to the unit “Production Department”, Eriga automatically generates the obligation for John Smith to complete the fire safety training. If you also assign “Periodic medical exam” to the same unit, John acquires that obligation as well — with no further intervention.
This model is powerful because it scales: adding a new action to a unit with 10 people creates 10 obligations at once. Adding a new person to a unit with 5 actions means that person immediately acquires all 5 obligations.
How it relates to other concepts
Section titled “How it relates to other concepts”- A resource can be assigned to multiple units (e.g., an employee who works at two sites)
- An action can be assigned to multiple units (e.g., mandatory training for all departments)
- Compliance obligations arise from the intersection: resources and actions in the same unit, with a compatible resource type
- Roles are assigned per unit — they determine what each user can do and see
Eriga has four roles, organized on two levels:
Space-level roles
Section titled “Space-level roles”| Role | Permissions |
|---|---|
| Owner | Full control: space management, admin appointment, everything an Admin can do |
| Admin | Full operational management: structure (resources, actions, units), compliance (certificates, attachments), unit roles. Access to all units without explicit assignment |
The Owner is the person who created the space. Admins are appointed by the Owner.
Unit-level roles
Section titled “Unit-level roles”Assigned per unit by the Owner or an Admin:
| Role | Permissions |
|---|---|
| Operator | Compliance management: issues, updates, and revokes certificates, manages attachments. Cannot modify the structure (resources, actions, units) |
| Viewer | Read-only: can view everything but cannot make changes |
A user can have different roles on different units (e.g., Operator on “Head Office” and Viewer on “Warehouse”).
Practical example
Section titled “Practical example”A company with three locations might have these units:
| Unit | Resources | Actions |
|---|---|---|
| Head Office | 3 people | Training, Medical exam |
| Production Department | 3 people, 1 environment | Training, Medical exam, Equipment inspection |
| Warehouse | 2 pieces of equipment | — |
The “Warehouse” unit has no assigned actions, so the equipment in it has no compliance obligations. As soon as you assign an action (e.g., “Periodic equipment inspection”) to the unit, the equipment will automatically acquire that obligation.
Learn more
Section titled “Learn more”- Guide: managing units — how to create, edit, and assign resources and actions to units
- Roles and permissions — complete permission details for each role
- Compliance — how obligations generated by units determine conformity status