Fleet Management
Fleet targets remote desktop management at scale: aggregate many devices for unified onboarding, grouping and orchestration instead of operating one by one.
Fleet List
The Fleet page shows the devices manageable in the current organization, typically with:
- Online / offline status.
- Identity, grouping and basic attributes.
- Entry points to a device's detail or to start a remote session.
Fleet acts on the currently selected organization — switching orgs switches the visible fleet scope.
Device Grouping
Use device groups (admin, Access control area) to classify devices by purpose / region / environment, so orchestration can dispatch by group rather than picking devices one at a time.
From Fleet to Orchestration
To run the same operation across a batch of devices (inspection, collection, remediation), use Fleet Exec, dispatching by command template.
Architecture
The fleet side follows a thin host + central brain topology: hosts only gather evidence, while orchestration and decisions happen centrally in the manager. This keeps auth, audit and policy consistent at scale.
Model-generated diagnosis rollup reports (and each device's diagnosis) carry an "AI-generated" marking in the UI plus a machine-readable provenance mark, meeting the transparency obligation for AI-generated content; batch command-execution results are command output and are not marked this way.
Fleet diagnosis uses the organization's effective default / platform-fallback agent model for Allow screenshot. If that model is text-only, the page explains why the toggle is unavailable. The manager still rechecks the capability when the task is created and immediately before each target sends an actual image. Organization policy, owner authorization, and the host's local collection policy must also permit capture.
Related
- Cross-device execution: Fleet Exec.
- Visibility prerequisite: Device Access Authorization.