The agreement belongs in the same platform as the function it carries
isidaten ships several functions that are subject to co-determination under Section 87(1) no. 6 BetrVG or the staff representation acts: behaviour analytics, remote support, device health, human risk, phishing simulation, SIEM correlation, deception. Until now the underlying agreement sat as free text in individual module forms, without an end date and without deadline monitoring. The register keeps it as an object of its own and connects it via a dated coverage to the function that actually runs. Lock automation is off out of the box; whether a matter is subject to co-determination is judged solely by your organisation.
Agreements on enforceable co-determination continue after expiry until replaced; Section 87(1) no. 6 BetrVG is enforceable. An expired monitoring agreement therefore does not, as a rule, mean the function must be switched off. A voluntary one under Section 88 has no continued effect. The continued-effect field models both, pre-set from the statutory grounds.
The other modules query the lock only via a core interface. If the register is off, UEBA, remote support and the other functions run as without a register, with their own approvals. The same person who can switch the module off could also set the mode to "off"; locking by switching off would be theatre.
The agreement is the legal basis, the monitoring function is what runs, and the coverage connects the two for a period. One agreement can cover several functions, one function can have several agreements. The lock automation reads exactly this edge.
The release of a monitoring function stays evidenced, because the agreement carrying it sits next to it with term and continued effect.
Schedule a no-obligation demo – we will show you the module with your own use cases.
