The Reports section in Trio MSP provides managed service providers with a centralized reporting engine designed for cross-organization visibility, auditability, and operational control. Reports are generated from normalized device, policy, and command data collected continuously by the Trio platform and scoped strictly per organization to maintain tenant isolation.
From an MSP perspective, this module replaces manual exports and fragmented tooling by allowing operators to generate consistent, repeatable reports across different customers, regions, and license states—without switching portals or contexts.
Built-In Reports Overview
Built-in reports are predefined report templates that map directly to common MSP operational and compliance needs. Each report pulls from authoritative backend sources such as the device inventory service, policy engine, and command execution logs.
Rather than exporting raw logs, these reports present aggregated, structured datasets that reflect the current and historical state of managed environments.
Available Device Fleet Reports
These reports focus on device lifecycle, configuration state, and enforcement outcomes:
Device Inventory Report
Provides a complete snapshot of enrolled devices, including platform, OS version, ownership model (COD/BYOD), and enrollment status.Device Group Assignment
Shows how devices are mapped to static or dynamic groups, validating targeting logic used by policies and software deployments.Policy Deployment Summary
Surfaces whether configuration and security profiles were successfully applied, failed, or are pending, enabling quick detection of enforcement gaps.Software Deployment Compliance
Compares assigned applications against actual installation state to identify drift from the desired configuration.Kiosk Mode Enforcement Report
Confirms which devices are operating in kiosk mode and whether enforcement matches the expected configuration.Command Execution Summary
Acts as an audit log for all remote commands executed through the Command Center, including execution status and timing.
Report Execution Modes
Trio MSP supports both immediate and scheduled report generation. These modes serve different operational purposes but rely on the same underlying data sources.
Immediate Reports (On-Demand)
Immediate reports are used for ad-hoc analysis, troubleshooting, or one-time exports. When triggered, Trio generates a point-in-time snapshot of the selected data.
How to run an immediate report:
Navigate to Activity → Reports
Select the required report type
Click Run Report
Choose Immediate report
Review or edit selected columns
Select the target organization
Click Continue
The report is generated asynchronously to avoid blocking the UI. Once complete, the file becomes available in Stored Reports, and a notification confirms readiness.
Scheduled Reports (Recurring)
Scheduled reports are designed for ongoing visibility, such as weekly compliance checks or customer deliverables. Instead of manual execution, Trio regenerates these reports automatically based on a defined schedule.
Scheduled reports retain:
Frequency (e.g., weekly)
Start date
Column selection
File format
⚠️ Important behavior:
If a report has already been scheduled, modifying its schedule will override the previous execution date, ensuring only one active schedule exists per report definition.
To schedule a report:
Open the desired report
Select Scheduled reports
Define frequency and start date
Confirm column selection and format
Select the organization
Save the schedule
Each execution produces a new report artifact while preserving historical runs for traceability.
Column Selection and Data Control
Every report supports column-level configuration, allowing MSPs to control exactly which attributes are exported. This is particularly important when reports are shared externally or used for audits.
Typical selectable fields include:
Device identifiers and platform metadata
Ownership and enrollment attributes
Policy compliance and deployment state
Software and command execution details
This flexibility allows the same report type to be reused for internal engineering analysis or customer-facing summaries without redefining the report itself.
Organization Scoping and Tenant Isolation
All reports in Trio MSP are generated within a single organization context. The organization selector ensures that data is never mixed across tenants.
The selection table supports:
Search by organization name
Sorting by name
Filtering by region, owner, or license status
This design ensures MSP operators can safely manage large portfolios while maintaining strict data boundaries.
Output, Storage, and Notifications
Reports are exported in XLSX format, optimized for spreadsheet analysis and long-term retention. Once generation starts, the system queues the job and displays a status notification.
When the report is ready:
It is stored under Stored Reports
A success notification confirms availability
An optional email notification delivers the download link
This asynchronous delivery model ensures reporting does not impact portal performance, even for large datasets.
Why This Matters for MSP Operations
From a technical standpoint, Trio MSP reporting enables:
Consistent, repeatable reporting across customers
Reduced manual data extraction
Reliable audit trails for policies and commands
Clear separation between real-time diagnostics and scheduled compliance outputs
By combining inventory, policy enforcement, and execution data into a single reporting system, Trio MSP provides a reporting layer that aligns with real-world MSP workflows, not just raw data export.