What it contributes
- Device enrollment, identity, ownership, and liveness
- Configured AI activity and device inventory signals
- Agent, collector, and browser-extension status where present
- Health, permission, diagnostic, and command results
Exact collection behavior is controlled by workspace configuration and device
policy. Do not infer that every visible data type is enabled on every device.
Lifecycle
1
Prepare deployment
Use the workspace Deployment area to obtain the installation path intended
for your environment.
2
Enroll the device
The installer registers the endpoint to the workspace using its deployment
credentials.
3
Bind ownership
Confirm the enrolled device is associated with the correct person. Unbound
devices remain visible for administrative follow-up.
4
Apply policy
Workspace device policy controls which endpoint components and commands are
allowed to run.
5
Monitor health
Use Devices to review online state, component state, permissions,
diagnostics, and recent commands.
Administrative controls
The device detail view exposes identity and owner information, health guidance, permissions, diagnostics and repairs, controls and policy, command history, and restricted destructive actions. Availability depends on role and device state.Plan deployment and privacy
Review fleet rollout, health operations, and workspace data controls.