Skip to main content
Visibility separates fleet rollout, device operations, component policy, and data privacy into dedicated administrative controls.
Review deployment coverage, device ownership, online state, and installed component types. Filters include unbound, offline, collectors, endpoint agents, command-line sensors, and browser extensions.

Deployment sequence

1

Define collection and privacy

Decide which sources are required and configure privacy and device policy before deployment.
2

Select the workspace artifact

Use the current package or managed-deployment artifact exposed in Settings → Deployment.
3

Pilot

Deploy to a controlled group and verify enrollment, ownership, permissions, health, and expected activity.
4

Expand

Roll out through your endpoint-management system while monitoring offline, unbound, and unhealthy devices.
5

Operate

Review diagnostics and command history, manage approved versions, and update policy as requirements change.

Privacy review

Before rollout, document:
  • The business purpose and authorized reviewers
  • The collection paths enabled for each device group
  • Redaction and privacy-mode settings
  • Employee notice, retention, and access requirements
  • The escalation path for incorrect identity, ownership, or captured data
Deployment mode determines where the data plane runs. See the platform deployment and security documentation for architecture-level controls.

Deployment architecture

Review hosted and customer-managed deployment concepts.

Security and privacy

Review platform-wide security and privacy boundaries.