Summary: Displays key information and operating status of the device.

Applications: View and manage applications installed on the device.

Policies: Show the device’s associated device policies, app policies, and compliance status.

Device Groups: Display the groups the device belongs to and inherited policies.

Device: View hardware, system, and network information.

Restrictions: Display and adjust restricted features (e.g., USB, Bluetooth).

Location Tracking: Support for real-time device location and historical route playback.

Operation Logs: Record administrator actions performed on the platform.

System Logs: Record system operation and compliance logs automatically reported by the device.

Provide IT administrators with a single device view, avoiding dispersed queries.

Support lifecycle-wide device monitoring and operations.

Enhance enterprise compliance management, application control, and troubleshooting.

Reduce manual maintenance costs and improve response time through remote operation capabilities.

View real-time operating data (e.g., memory usage, battery level);

Quickly verify device registration time, manufacturer, model, and serial number;

Access OS parameters such as version, patch level, and kernel version;

Check if the device meets platform compliance requirements and identify non-compliance reasons;

Review network identifiers (IMEI, Wi-Fi MAC, etc.) to assist with connectivity or troubleshooting;

Confirm security configurations (PIN/password, ADB, encryption, protection mechanisms) to ensure alignment with enterprise security policies.

Some data (e.g., battery level, memory usage) is based on the latest device report; values may be delayed if the device is offline.

Compliance checks depend on the device’s OS version and strategy configuration; different strategy combinations may trigger a “non-compliant” status.

Certain network fields (e.g., IMEI, ICCID, phone number) may be empty or unsupported depending on the device.

Security configurations (e.g., ADB, developer mode) should be enabled only when necessary, to avoid security risks.

Health Check: IT administrators quickly evaluate memory usage, battery level, and security settings to assess device health.

Compliance Check: Validate compliance after applying new strategies via the Summary tab.

Troubleshooting: Use network and system data (e.g., IMEI, patch level) to locate anomalies or compatibility issues.

Asset Management: Track devices using registration time, model, and serial number for inventory and audit purposes.

Application data comes from the latest report from the device; information may be delayed if the device is offline.

Application status is controlled by Application Publish Policy or Application Update Policy; some information is only displayed when policies are linked.

If no allow/deny rules are configured, the corresponding sub-tab may be empty.

The User Applications List only displays user-level apps; system apps are excluded.

Administrators can quickly locate target apps using the search box by app name or package name.

Compliance Check: Verify quickly whether the device complies with enterprise application control policies using the allowed/blocked lists.

Troubleshooting: When users report issues installing or using an app, check here to confirm if restrictions apply.

Operational Monitoring: Monitor critical business apps (e.g., POS software) to ensure proper installation and linkage to the correct publish policy.

Application Asset Management: Understand application deployment status on a single device to support version updates and maintenance planning.

A device may be associated with multiple policies simultaneously; the system calculates the final effective result based on the “module-level merge, latest version takes precedence” principle.

For duplicate policy types (e.g., multiple Wi-Fi configurations), the latest applied configuration takes effect.

Compliance status depends on device-side reporting and comparison with policies, which may be delayed if the device has not synced.

If a deployed policy requires changes, it must be updated in the policy center and redeployed.

Compliance Validation: Ensure devices adhere to enterprise security policies and investigate specific non-compliance causes.

Operational Troubleshooting: Review current effective policies and deployment history to identify possible conflicts causing abnormal device behavior.

Version Control: Compare policy versions and history to ensure devices are running the latest policies.

Audit Evidence: Export policy history and compliance status for enterprise compliance and security audits.

View Group Information: Display group name, number of devices, number of linked policies, whitelist/blacklist apps, operator, and last modification time.

Add to Group: Add the current device to other existing groups.

Remove from Group: Remove the device from selected groups.

Operational Tracking: Confirm the responsible operator for group adjustments.

A device can belong to multiple groups, inheriting policies from all groups.

When in multiple groups, policies are merged using the rule: merge across modules, with the latest version taking precedence.

Removing a device from a group means it no longer inherits that group’s policies, which may affect configuration and compliance.

Group changes take effect immediately. It is recommended to perform adjustments during off-peak business hours to avoid service impact.

Operator actions are logged for audit and traceability.

Organizational Management: Manage devices across different regions, stores, or business units via groups to improve operational efficiency.

Policy Inheritance: Apply policies at the group level to simplify repetitive configuration for individual devices.

Troubleshooting: Check device group membership and linked policies to identify potential causes of abnormal behavior.

Dynamic Adjustment: Reassign devices to new groups when they move to different business contexts or regions to ensure proper policy and application delivery.

Device information is reported by the device; if the device is offline, there may be delays.

Network information may vary by device type (e.g., MEID and ICCID may be empty on some models).

If security configurations do not meet enterprise policy requirements, the device may be flagged as non-compliant.

Password requirements are controlled by the deployed policies; if no password policy is configured, this section may show “No Requirements.”

Certain security risk alerts (e.g., “Hardware verification failed”) should be evaluated in the context of both policy and device conditions.

Asset Management: Build device records with Device ID, model, and serial number.

Compliance Audits: Verify whether devices meet corporate password and security requirements.

Troubleshooting: Diagnose connection or identifier issues using network information.

Security Protection: Detect and respond when ADB or developer mode is enabled, reducing risk exposure.

Security Restrictions: Whether camera access, screenshots, microphone, developer mode, or factory reset are allowed.

System Updates: Configuration of system update installation policies.

Network & Connectivity: Whether airplane mode, Wi-Fi, Bluetooth, NFC, USB file transfer, hotspot sharing, etc., are allowed.

Other Restrictions: Policies related to app installation/uninstallation, screen timeout, wallpaper and theme changes, and screen resolution adjustments.

All data in this tab is reported by Google ADP. The platform only displays the data and does not support direct modification.

Reporting content may vary depending on device model and OS version.

If restrictions conflict with enterprise policies, the latest deployed policy takes precedence.

Restrictions such as USB file transfer and hotspot sharing involve potential security risks and should be carefully managed based on business needs.

Restrictions like screen timeout, wallpaper changes, and resolution settings mainly affect user experience and are not recommended to change arbitrarily.

Compliance Review: Verify whether device restrictions comply with enterprise security and management standards.

Troubleshooting: Identify whether functional issues (e.g., camera or Wi-Fi not working) are caused by restriction policies.

Risk Control: Prevent data leaks caused by risky features such as USB file transfer, ADB, or hotspot sharing.

Experience Optimization: Confirm whether endpoints support customized experiences such as fixed resolution or unified wallpapers.

Real-time Location Display: Visually show the device’s current position on a map (or satellite image).

Location Details: Display the most recent report time, detailed address, and latitude/longitude coordinates.

Tracking Status: Indicate whether the device has location tracking enabled.

Feature Operations: Support enabling Lost Mode and viewing Location History.

Location data relies on device reporting; if the device is offline, updates may be delayed or unavailable.

Different device models may have varying location accuracy due to hardware differences.

Enabling Lost Mode may trigger additional security measures (e.g., screen lock, forced location reporting).

If location permissions or services are disabled on the device, the latest location cannot be obtained.

Asset Tracking: Administrators can quickly determine the distribution of devices across different regions.

Theft Recovery: When a device is lost, enable Lost Mode to continuously track its position.

Operations Scheduling: For large-scale deployments, use location tracking to assign maintenance tasks efficiently.

Security Monitoring: Analyze historical movement patterns to detect abnormal relocation or misuse.

Filter logs by operation type, time range, or operation ID.

View detailed records of device actions such as policy distribution, restoration, or modification.

Analyze reasons for failed operations to aid in issue identification and resolution.

Operation logs only record manual actions initiated from the platform, excluding system-automated actions (which are recorded in the System Logs tab).

Log entries display the latest device-reported results; delays may occur if the device is offline or unresponsive.

Logs are paginated by default, with options to adjust items per page or export logs.

Only administrator accounts with proper log viewing permissions can access full records.

Audit Tracking: Export complete operation logs during security or compliance audits as verifiable evidence.

Issue Diagnosis: Verify whether failed device configurations were due to policy distribution errors or abnormal operations.

Accountability: Use the "Operator" field to identify responsible administrators for specific actions.

Routine Monitoring: Regularly review logs to ensure device operations and policy distributions are functioning as expected.

Query various system operation records executed by the device.

View key fields such as operation ID, operation type, execution result, duration, and start/end times.

Trace whether the device correctly received and executed assigned policies or commands.

System logs are automatically reported by the device, and the platform only collects and displays them.

They record only system-level execution results, complementing the Operation Logs (which track manual actions by administrators).

If the device is offline or has an unstable network, logs may be delayed or missing.

Execution results include success/failure statuses; failure causes must be further analyzed using log details.

It is recommended to regularly export logs for long-term archiving and security audits.

Execution Confirmation: Verify through logs whether a device successfully applied a newly issued policy.

Issue Diagnosis: Identify specific causes of failure when a device does not reach the expected state.

Performance Analysis: Use duration data to assess device efficiency and optimize policy configurations.

Compliance Auditing: Export system logs as important evidence for operational and security audits.