> ## 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 and rollout > Enroll endpoints, deploy collection components, monitor health, and manage release policy. The device control plane connects organization-managed endpoints to Oximy and provides the operational state required to run endpoint collection reliably. ## Enrollment Devices can be enrolled through organization deployment tokens, managed rollout, or supported self-enrollment paths. Enrollment establishes a device identity that can be linked to a person through the shared identity graph. MDM-provided identity is a useful signal, not the only enrollment mechanism. Unresolved devices remain visible for review rather than being discarded. ## Endpoint types | Component | Role | | ----------------- | -------------------------------------------------------------------- | | Endpoint agent | Network-level AI activity capture and device control | | Browser extension | Web AI activity with browser context | | Local collector | Coding sessions, local agents, skills, MCP, and configured artifacts | | CLI component | Command-line deployment and collection paths | ## Fleet operations Administrators can review: * Enrollment and ownership. * Online and offline state. * Installed component and version. * Sensor, proxy, and collection health. * Diagnostic information and endpoint-reported errors. * Commands, controls, and update state. ## Release controls Workspace settings include device policy and endpoint version controls. Administrators can coordinate rollout, constrain permitted versions, and use historical synchronization when previously collected data must be backfilled. Compare endpoint, browser, local, integration, and Relay data.