Who is this article for?

Administrators responsible for organisation management.

Administrator role is required.

Organisations act as the parent container for departments, users, spaces, and inspection schedules.

This article breaks down these elements to help you better understand how to manage organisations within your system.

1. Organisation

Organisations define the top-level structure for your site, containing departments, users, spaces, and inspection schedules. This configuration ensures that your hierarchy aligns with how your institution or company operates in real life.

1.1. Department list

All departments created within the system are grouped under their parent organisation. This view allows you to quickly review which departments are active, confirm assigned contacts, and drill into departmental rosters.

Example

Academia - School of Medicine → Department of Microbiology

Manufacturing - North Plant → Quality Assurance Department

Construction - Project A → Safety Operations

1.2. Organisation roster

The roster allows area managers or administrators to receive notifications at the organisational level. This is distinct from the users list, which displays all users across departments and their assigned roles.

Use it to:

• Designate escalation contacts for safety alerts.
• Add senior leadership for visibility into audit or compliance notifications.
• Centralise communication for multi-department organizations.

1.3. Room list

Displays all rooms assigned within the organisation, including labs, shops, or work areas. This list is helpful for cross-departmental safety inspections or space-level reporting.

1.4. Inspection template schedule

Lets you define recurring inspection cycles at the organisation level.

1.5. Users list

Shows all users associated with the organisation and their assigned roles. This list updates automatically as users are added or removed from departments.

1.6. Recent inspections

Displays a running history of the most recent inspections conducted across the organisation, whether tied to rooms, assets, or users. Use this view to quickly confirm inspection frequency compliance across multiple departments.

2. Department

Departments define the next level in your organisational hierarchy. They link directly to organisations and act as the primary container for users, spaces, and inspection schedules. This setup ensures reporting, training, and inspection data align with your operational structure.

2.1. Department roster

The roster lists all users belonging to a department. Users in this roster can receive notifications and access department-level information (e.g., inspection results or corrective actions).

Escalation emails can be configured to route to the department contact, roster, or user list.

Example

Academic - Add PIs and lab managers to receive inspection results.

Manufacturing - Include supervisors and EHS coordinators for their production line.

2.2. Room list

Displays all rooms assigned under the department. Rooms can be filtered by room type to assist in scheduling inspections or reviewing occupancy assignments.

2.3. Inspection template schedule

Lets you define recurring inspection cycles at the department level.

2.4. Users list

Displays all users who belong to the department. This differs from the inspection roster, which only lists those who receive inspection reports or corrective actions.

Use the department users list to verify everyone who should have access to training, assets, or space assignments under that department.

Further reading

• Adding an organisation
• Adding a department