> For the complete documentation index, see [llms.txt](https://docs.we360.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.we360.ai/reference/product/workforce-productivity/screen-tracking.md).

# Screen Tracking

## Overview

Screen Tracking captures visual representations of the employee's active desktop environment. It serves as both an auditing tool and a core feature of the organizational productivity profile, providing context to the time logged.

## Supported Platforms

* **Desktop Agent**: Captures the screenshots on Windows, macOS, and Linux — including **Citrix, RDP, and VDI environments**.
* **Web Dashboard**: Managers and administrators can review captured screenshots within the user's timeline activity on the We360.ai administration portal.

## Functionality

The We360.ai desktop agent quietly captures the screen at pre-defined intervals across all supported platforms (Windows, macOS, and Linux) and securely uploads them for review. Screen Tracking works identically in both Standard and Stealth (silent) modes.

* **Configurable Captures**: Administrators govern the capture frequency through the compliance settings. The screenshot capability can be explicitly disabled for specific teams or individual users to meet varying privacy requirements.
* **Privacy & Compliance**: Configurable options exist to adjust the screenshot blur level or restrict the ability for managers to download screenshots. This protects sensitive data while ensuring enterprise-level compliance.
* **Timeline Integration**: Extracted screenshots fuel the granular user timeline logs on the front-end, allowing managers to see exactly what an employee was focusing on during specific intervals.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.we360.ai/reference/product/workforce-productivity/screen-tracking.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
