Skip to main content
Syteca tracks idle events through two related parameters that work together. “Register IDLE event when user is inactive” fires on user-inactivity timeout (configurable in minutes). “Detect System IDLE events” fires on OS-level sleep, hibernation, or display power-off. Combined, they let you tune exactly when idle gets recorded — useful for filtering out genuine breaks while avoiding false-positives during meetings or focus work without mouse/keyboard activity.
Applies to: Windows Clients, macOS Clients. The Linux Client also supports “Register IDLE event when user is inactive” — same checkbox, same Timeout (mins) field, on the Monitoring [Linux] tab. It’s only implemented for GUI sessions; it can’t register idle events in local terminal or remote SSH sessions.

​
Where to find both parameters

Both checkboxes live on the Editing Client / Editing Client Group page, on the Monitoring [Windows/macOS] tab, in the Monitoring Parameters section at the top.

​
Register IDLE event when user is inactive

If the Register IDLE event when user is inactive checkbox is selected, Syteca registers an idle event whenever there’s no Client activity (no mouse movement, no key pressing) for longer than the Timeout (mins) value specified.

​
Detect System IDLE events

If the Detect System IDLE events checkbox is selected, Syteca registers an idle event when the operating system itself enters a low-activity state. The trigger differs by OS:

​
How the two parameters interact

The behavior matrix when neither parameter is checked, one is checked, or both are checked:

​
Configurations for specific scenarios

To avoid registering idle during online meetings where the user is on a video call without touching mouse or keyboard:
  • Both checkboxes OFF (example #2 above), OR
  • Detect system IDLE events ON, Register IDLE event ON with Timeout 999 (example #4 above) — system events still fire (sleep, screen-off) but the timeout is effectively disabled
The first option is simpler. The second keeps system-event detection working so you still capture lock-screen idle from screensaver kicking in. To enforce strict 15-minute idle detection for compliance recording:
  • Register IDLE event ON, Timeout 15 — fires on inactivity. Add Detect system IDLE events ON if you also want sleep/hibernation events.

​
Interaction with recording

The idle parameters also affect user activity recording. If “Record user activity periodically” is enabled with “Stop recording after IDLE event” also enabled, screen captures pause once an idle event fires — reducing data volume during inactive periods. They resume when activity resumes.

User activity recording

Where the “Stop recording after IDLE event” option lives.

Auto-cleanup

Lifecycle for the data idle-aware recording produces.

Linux Clients

Linux Client documentation including its Register IDLE event variant.

Sessions

Where idle events appear in session metadata.