Co-determination out of the box
The module ships locked. It can only be enabled with a confirmed legal basis, a reference to the works agreement, a linked processing activity and a retention period.
The control layer above your existing remote support tools
Remote support is the most far-reaching access in IT operations: whoever takes over a screen sees everything on it. That is precisely why remote screen control requires works council co-determination under German law, regardless of intent – settled case law holds that objective capability for monitoring conduct and performance is enough. The module draws the consequence and stays locked until the legal basis is documented. After that every session becomes a procedure: requested with a purpose and a ticket, approved under the four-eyes principle, limited to a time window and recorded in a hash-chained event log. The transmission itself stays with the tool already in your building.
The module ships locked. It can only be enabled with a confirmed legal basis, a reference to the works agreement, a linked processing activity and a retention period.
Every session needs a purpose and a ticket, a second person to approve it and a time window after which it ends by itself. Emergencies are possible but require a justification and stay marked as such.
Each session’s event log is sequentially numbered and linked by a hash chain. Viewing a recording is logged as well, with a reason and the person who approved it.
Intune for the Windows laptops, SSH for the Linux servers, MeshCentral for the rest: several back ends in parallel are the norm, each with its own rules for approval, ticket requirement and maximum duration.
Remote support your works council can support, because the boundary is drawn by the procedure rather than by the administrator’s good intentions.
Schedule a no-obligation demo – we will show you the module with your own use cases.