What determines the recipient of a notification
Teams decide who is assigned and notified in work permits, reports and location alerts. The administrator manages them in the settings. This gives one place of configuration instead of distribution lists scattered across emails and phones.
Each team groups the people responsible for a part of the plant: it has areas from the map tree (hall, area, line, location), members, roles in jobs and the report categories it handles. The recipient of a notification therefore follows from the place of the event and the type of matter, not from a manual choice by the duty officer under pressure.
What happens when a person without valid training scans a card at the gate
A scan by a person without valid training at the gate creates an alarm and notifies the coordinator of that person's company. The notification goes to the company the employee comes from, not to a random duty officer in the plant, because the company is the one able to complete the training.
Calls are merged into one per company within a 55-minute window. If several people from the same contractor are stopped at the gate in a short time, the coordinator receives one call, not a dozen.
The default contact person of a company
An external company may have a default contact person, used as its coordinator. It is worth setting this up when the company is created in the system, because without a coordinator the alarm has no clear addressee on the contractor's side.
Calls to the coordinator with 12 scans in a 55-minute window
How a team limits reports to its own area
A team can have an option that limits reports to its own area. When it is enabled, people in the hall team do not receive reports from a distant warehouse, which reduces unnecessary notifications and keeps the remaining ones credible.
When designing teams, start from the map tree of the plant. Every area should have at least one responsible team, and team boundaries should not overlap too much. Otherwise the notification returns to the question of who should actually react.
Why Secretariat does not receive refusal-of-entry alerts
Secretariat does not receive refusal-of-entry notifications and is not a gate account. This is a deliberate design choice so that it is not mixed up with security. Reception handles visitors and refusals at the gate are handled by security.
If in your plant reception and security are the same group of people, the solution is not to change the secretariat role. It is better to assign specific people to a gate account as well, explicitly and with a record in the implementation document.
How to check the configuration before going live
The most reliable way is a full rehearsal: a test alarm for each category and each area, with a record of who received it and after how long. The test reveals gaps, such as an area without a team or a company without a coordinator, before they appear in a real incident.
The system works as an independent complement to the client's existing systems (access control, time and attendance, HR, ERP), so the owners of those systems should know the list of alarm recipients. This prevents a situation where two groups react to the same event and a third knows nothing about it.
- every area from the map tree has an assigned team,
- every external company has a coordinator or a default contact person,
- a test alarm for every report category,
- the response time recorded in the test protocol.
Checklist
Video
Frequently asked questions
Who gets the notification when a contractor's employee has no valid training?
The coordinator of that employee's company. The alarm is created at the gate scan, and calls to the same company are merged into one within a 55-minute window.
Where are location alert recipients set up?
In teams, which the administrator manages in the settings. A team has areas from the map tree, members and the categories it handles.
Can a team see only the reports from its own hall?
Yes, a team can have an option that limits reports to its own area. It is worth enabling where areas are clearly separated.
Why did Secretariat not receive a refusal-of-entry notification?
It is a design decision: Secretariat is not a gate account. Security handles refusals, and reception deals with visitors.
Let us check the alarm paths in your plant
In a demonstration we will show how teams and company coordinators set the notification recipients, and we will help you plan a full rehearsal.
Let's talk