Help Center
Monitoring agent
Installing, verifying, updating and removing the agent, and what it does and does not collect.
How do I install the monitoring agent?
Download the agent installer from the Agents page (if your company has downloads enabled) and run it on the machine. During setup it enrols with your company's enrolment key. Installation needs local administrator rights on that computer.
How does the agent start automatically?
On Windows the agent installs a boot task that starts it at system start and a logon task for the user session, so it comes back after restarts and sign-ins without anyone launching it. A watchdog restarts it if it stops unexpectedly.
How do I verify the agent is running?
On the machine, look for the agent's visible tray icon — the agent is never hidden. In the console, open Agents and check the device's status and last-seen time, or Real-Time to confirm it is reporting activity.
How do I update the agent version?
Agent updates are managed centrally. When you publish a new release, agents pick it up on their next check-in and update themselves (a secure, verified swap). You can set a minimum version and block known-bad versions; a blocked agent is told to update before it can report.
How do I uninstall the agent?
Uninstall it like any Windows application from the machine (local administrator rights required). Once it stops reporting, the device shows offline in the console; remove or retire the asset record separately if you no longer need it.
What data does the agent collect?
Only what your company switches on. Attendance (session start/stop) and idle detection are on by default and count time, not content. Screenshots, live screen, recordings, clipboard, and app and website activity all ship switched off and must be enabled per company, department, team or person — and only after the employee acknowledges the monitoring notice.
Can the agent run as a Windows service?
Yes. The current agent runs a SYSTEM-level component at boot plus a session component at logon, so capture survives sign-out and restarts. This is handled by the installer; you do not need to configure it by hand.
What happens if the agent loses its configuration or credentials?
The agent keeps an atomic, backed-up configuration and can re-enrol itself if its credentials are lost, so a damaged install recovers on its own rather than going silent. Its self-update applies verified new builds and rolls back a bad swap.
Can I limit the agent to working hours?
Yes. Set a capture window (working hours) and blackout periods in the monitoring settings. Outside the window the agent does not capture content, which is useful for shift patterns and respecting off-hours.
What are the agent’s system requirements?
The agent runs on Windows and needs local administrator rights to install and network access to reach your console. It is lightweight and uses change-detection so it only sends captures when the screen actually changes.