# Managing Policy Reports in Hexnode UEM Policy Reports in Hexnode UEM provide real-time visibility into the deployment and compliance status of configuration profiles. These reports serve as the definitive audit trail for **Policy-to-Device mapping**, allowing IT admins to verify which security restrictions are active on specific endpoints and identify non-compliant devices. **1. How do Policy Reports work? (The Compliance Framework)** -------------------------------------------------------------- Policy Reports function as the “Audit Layer” of the Hexnode Compliance Engine. While a **Policy** defines the rules (e.g., Password requirements, Wi-Fi settings), the **Policy Report** tracks the execution of those rules across the fleet. - **Logic Dependency:** A policy must be **Associated** with a device, user, or group before it generates data within these reports. - **Platform Support:** Reports aggregate data for **Android, iOS, macOS, Windows, tvOS, Linux,** etc. **2. Technical Specifications: The Report Categories** ------------------------------------------------------- Hexnode categorizes policy telemetry into 2 distinct data objects: **Report Type** **Primary Data focus** **Key Metrics Tracked** **Device Policies** The Policy Entity Policy Name, Platform, Association Count, Created time, Last Modified **Compliance Policies** The Security State Compliance Status (Compliant/Non-Compliant) **3. Auditing Policy Compliance** ---------------------------------- The **Policy Report (Device/Compliance)** is the most critical for Security Operations (SecOps). It uses a binary logic state to report on device health: - **Policy association state:** The device has successfully acknowledged and applied all payloads within the associated policy. - **Non-Compliant State:** The device has failed to apply one or more payloads, or a mandatory restriction (like a passcode) has been removed by the user. - **Targeting:** Use this report to isolate devices that require a Remote Action (e.g., “Scan Device”) to force policy re-application. **4. How to Generate and Automate Policy Reports** --------------------------------------------------- Follow these precise navigation paths to retrieve policy telemetry from the Hexnode portal. ### **Path A: View Devices Linked to a Specific Policy** 1. Navigate to **Reports > Built-in Reports > Policy > Device Policies**. [![Navigate to Reports, Built-in Report, Policy, Device Policies in the console to view the Policies reports in Hexnode UEM](https://cdn.hexnode.com/mobile-device-management/help/wp-content/uploads/2026/03/Device-Policies-reports-with-Policy-Reports-Hexnode-UEM.png "Device Policies reports with Policy Reports Hexnode UEM")](https://cdn.hexnode.com/mobile-device-management/help/wp-content/uploads/2026/03/Device-Policies-reports-with-Policy-Reports-Hexnode-UEM.png) 3. **Result:** Lists every managed device alongside its currently active device policies. ### **Path B: Identify Non-Compliant Endpoints** 1. Navigate to **Reports > Built-in Reports > Policy**. 2. Click on **Compliance Policies**. [![Navigate to Reports, Built-in Reports, Policy, Compliance Policies in the console to view the Policies reports in Hexnode UEM](https://cdn.hexnode.com/mobile-device-management/help/wp-content/uploads/2026/03/Compliance-policy-reports-within-Policy-reports.png "Compliance Policy reports within Policy Reports Hexnode UEM")](https://cdn.hexnode.com/mobile-device-management/help/wp-content/uploads/2026/03/Compliance-policy-reports-within-Policy-reports.png) 4. Use the **No.of Devices** column to isolate “Non-Compliant” devices. **5. Data retrieved from the policies report** ----------------------------------------------- An overview of the following attributes can be obtained from the reports within the Device/Compliance policies reports. **Available columns** **Meaning** **Number of devices** Displays the number of devices with which the policy is associated. **Policy name** Displays the name of the policy. **Version** Displays the number of times the policy has been edited. **Created time** The date and time when the policy is created. **Last Modified** The date and time when the policy is last modified. **Created By** Displays the email address of the technician who created the policy, or shows as **System** for system-generated policies.**Last Modified By** Displays the email address of the technician who recently modified the policy, or shows as **System** if modified by the system.**Status** Displays the current deployment status of the policy *(Success, Failed, Partially Successful)*.**6. Fetching the Device list of selected policies** ----------------------------------------------------- The “No.of Devices” column segregates the number of devices associated with the policies. Accessing it will give you enough information about the device and user attributes. [![Navigate to Reports, Built-in Reports, Policy, Device Policies in the console, and click on the No.of devices column to view more device details](https://cdn.hexnode.com/mobile-device-management/help/wp-content/uploads/2026/03/Policy-details-Policy-Reports-Hexnode-UEM.png "Device details in the Policy Reports Hexnode UEM")](https://cdn.hexnode.com/mobile-device-management/help/wp-content/uploads/2026/03/Policy-details-Policy-Reports-Hexnode-UEM.png) 1. **Device name:** Displays the name of the device. 2. **User:** Displays the name of the user associated with the device. 3. **Email:** Displays the username of the user associated with the device. 4. **OS:** Displays the operating system of the device. 5. **OS Version:** Displays the OS version of the device. 6. **Serial Number:** Displays the serial number of the device. 7. **Compliance Status:** Identifies whether the device is compliant or not. 8. **Status:** Displays the deployment status of the policy on the device *(Success, Pending, In Progress, Partially Successful, Failed, Cancelled, Initiated, Downloading, Installing)*. **7. Advanced Export & Scheduling** ---------------------------------------- - **Supported Formats:** Export reports as PDF for executive summaries or CSV for ingestion into third-party SIEM/BI tools. - **Automation:** Click [schedule reports](https://www.hexnode.com/mobile-device-management/help/how-to-schedule-reports-on-hexnode-uem/) to configure recurring email audits (Daily, Weekly, or Monthly) to ensure continuous compliance monitoring.