Skip to main content
Collection is operated across Settings → Deployment, Devices, Device Policy, Privacy, and Historical Sync.

​
Deploy and verify

1

Choose the component

Use Deployment to obtain the endpoint agent, collector, extension, CLI, script, or managed-deployment artifact required for the environment.
2

Pilot the rollout

Start with a representative group before expanding to the full fleet.
3

Verify Devices

Open Devices and use Unbound, Offline, Collectors, Sensors, CLI Sensors, or Extensions to find incomplete coverage.
4

Resolve identity and health

Bind unassigned devices to the intended person and investigate offline or unhealthy components.

​
Enable local AI-session collection

Open Device Policy → Data collection, enable Collect local AI sessions, and confirm Turn on collection. The policy is workspace-wide, but a managed per-device setting can take precedence.

​
Run a historical scan

Open Historical Sync, enable Enable backtrack scanning, choose the Start date, then select Save changes. Connected devices rescan the configured period.
Changing the historical-sync date does not delete data that was already uploaded. Use the applicable data-management process for deletion.
The Privacy page describes the current collection posture. Do not assume that a displayed posture is an editable workspace control unless the page exposes a supported change action.

Compare collection components

Understand the browser extension, local collector, and endpoint collection boundaries.