Concept: Safety Incident Security
Safety incidents have 2 components with separate contextual security:
- A safety incident report associated with a business site location.
- One or more involved parties that belong to supervisory organizations.
This contextual security applies to all safety incident tasks, reports, business processes, and report data sources. This means:
- Safety incidents with an involved party are accessible to roles on either the location hierarchy or supervisory organization.
- Safety incidents without an involved party are accessible only to roles on the location hierarchy, since there's no supervisory organization.
The table displays examples of access to safety incidents for different roles:
Example | Security Group | Access |
|---|---|---|
Safety Administrator (or similar role) | User-based |
|
Safety Partner (or similar role) | Role-based (location hierarchy) |
|
Manager | Role-based (supervisory organization) |
|
Worker | Employee as Self |
|
Reporter | Any security group | Can see all safety incidents that they reported, as long as they are in a security group assigned to safety domains. |
When you use the
Report Safety Incident
task to add an involved party to a safety incident report, you only see the Nature of Injury/Illness
collapsible section. This is because the supervisory organization context isn't available. You see the additional tabs in the Update Safety Incident
task when the involved party provides context for security access. Alternatively, you can assign the
Employee as Self
and Contingent Worker as Self
security groups to the Self-Service: Safety Incidents
domain to display the additional tabs in the Report Safety Incident
task. However, these collapsible sections are visible to workers if they have permission to view safety incidents.