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

# Devices, deployment, and privacy

> Roll out Visibility collection, monitor endpoint health, and configure workspace data controls.

Visibility separates fleet rollout, device operations, component policy, and data privacy into dedicated administrative controls.

<Tabs>
  <Tab title="Devices">
    Review deployment coverage, device ownership, online state, and installed
    component types. Filters include unbound, offline, collectors, endpoint
    agents, command-line sensors, and browser extensions.
  </Tab>

  <Tab title="Deployment">
    Obtain the installation packages, scripts, profiles, or managed-deployment
    artifacts made available for your workspace. Use your existing endpoint
    management and change-control process for fleet rollout.
  </Tab>

  <Tab title="Device policy">
    Control which endpoint agents, collectors, and administrative commands are
    allowed to run. Device-policy changes are restricted to administrators.
  </Tab>

  <Tab title="Privacy">
    Configure workspace redaction, privacy mode, and data controls. These
    settings are also administrator-only.
  </Tab>
</Tabs>

## Deployment sequence

<Steps>
  <Step title="Define collection and privacy">
    Decide which sources are required and configure privacy and device policy
    before deployment.
  </Step>

  <Step title="Select the workspace artifact">
    Use the current package or managed-deployment artifact exposed in
    **Settings → Deployment**.
  </Step>

  <Step title="Pilot">
    Deploy to a controlled group and verify enrollment, ownership, permissions,
    health, and expected activity.
  </Step>

  <Step title="Expand">
    Roll out through your endpoint-management system while monitoring offline,
    unbound, and unhealthy devices.
  </Step>

  <Step title="Operate">
    Review diagnostics and command history, manage approved versions, and update
    policy as requirements change.
  </Step>
</Steps>

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

<Info>
  Deployment mode determines where the data plane runs. See the platform
  deployment and security documentation for architecture-level controls.
</Info>

<Columns cols={2}>
  <Card title="Deployment architecture" icon="server-cog" href="/docs/platform/deployment">
    Review hosted and customer-managed deployment concepts.
  </Card>

  <Card title="Security and privacy" icon="shield" href="/docs/platform/security-privacy">
    Review platform-wide security and privacy boundaries.
  </Card>
</Columns>