> ## Documentation Index
> Fetch the complete documentation index at: https://syteca.com/docs/llms.txt
> Use this file to discover all available pages before exploring further.

# Idle Event Detection

> Two parameters that together control when Syteca registers idle events — Register IDLE event when user is inactive (timeout-based), and Detect System IDLE events (sleep/hibernation/screen-off). Both work together to define the system's idle behavior.

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.

<Note>
  **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.
</Note>

## 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.

| Parameter        | Range            | Default    |
| ---------------- | ---------------- | ---------- |
| `Timeout (mins)` | 1 to 999 minutes | 15 minutes |

## 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:

| Platform                                               | Triggers when                                                                                                   |
| ------------------------------------------------------ | --------------------------------------------------------------------------------------------------------------- |
| **Windows 11 / 10 / Server 2022 / 2019 / 2016 / 2012** | The Client computer enters sleep or hibernation, or the screen turns off automatically based on power settings. |
| **macOS**                                              | The user has been inactive for more than 15 minutes (fixed, not configurable on Mac).                           |

## How the two parameters interact

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

| `Detect system IDLE events` | `Register IDLE event when user is inactive` | `Timeout (mins)` | Result                                | Idle event fires after                              |
| --------------------------- | ------------------------------------------- | ---------------- | ------------------------------------- | --------------------------------------------------- |
| **Off**                     | **On**                                      | 15 *(default)*   | Idle event registered on timeout only | 15 minutes of no input                              |
| **Off**                     | **Off**                                     | —                | **No idle event** registered, ever    | —                                                   |
| **On**                      | **On**                                      | 20               | Either trigger fires the idle event   | 20 minutes of no input, OR system sleep/screen-off  |
| **On**                      | **On**                                      | 999 *(max)*      | Either trigger fires the idle event   | 999 minutes of no input, OR system sleep/screen-off |

## 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](/docs/session-monitoring/recording/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.

## Related

<CardGroup cols={2}>
  <Card title="User activity recording" icon="video" href="/docs/session-monitoring/recording/user-activity-recording">
    Where the "Stop recording after IDLE event" option lives.
  </Card>

  <Card title="Auto-cleanup" icon="trash" href="/docs/administration/clients/parameters/auto-cleanup">
    Lifecycle for the data idle-aware recording produces.
  </Card>

  <Card title="Linux Clients" icon="terminal" href="/docs/administration/clients/linux">
    Linux Client documentation including its Register IDLE event variant.
  </Card>

  <Card title="Sessions" icon="list-video" href="/docs/session-monitoring/sessions-list">
    Where idle events appear in session metadata.
  </Card>
</CardGroup>