Site Blocks
Block a security officer from a specific site, usually at a customer's request. The strictest block in the system.
Blocking and unblocking
The employee profile has a tab for site blocks. You select a site, optionally enter a reason, and create the block. The block applies indefinitely until someone removes it.
This is work for dispatchers and is not reserved for owners. If someone sets an existing block again, this overwrites the reason and author.

How the block works
In three places at the same time:
- Assigning and accepting are rejected. If a reason is stored, it appears in the message.
- The matcher does not suggest the security officer for this site.
- In the shift board, the security officer does not see shifts at this site. They are not told that they are blocked and never see the reason.
Cannot be overridden
Unlike double booking and Arbeitszeitgesetz rules, a site block cannot be bypassed with a reason. There is no switch for this. The only option is to remove the block.
This is intentional: a block requested by a customer must not be dismissed with a click during daily operations.
Limit: The block is linked to the site. Orders without a site therefore do not recognize it.
Related
- Team and RolesSix roles, with a finely structured set of permissions above them. What someone sees is determined by the permission, not the role alone.
- Duty Roster and SchedulingSite rows on a timeline. Draw, resize, split and assign. A set of rules checks every assignment in the background.
- Organizational UnitsFor companies with several branches: who can see which sites, orders, and security officers.
Updated on: 03.09.2026