1. Summary Tab
Notes:
All information is reported by the KC client on the device and may have some delay.
Compliance status is based on real-time comparison between device status and policy configuration. After a policy change, wait for the next report for accurate status.
Location information depends on location permissions enabled on the device. If disabled or signals are weak, the map may appear empty.
1.1 Feature Overview
The "Summary" tab presents key status information of the device to help users quickly understand its operational and compliance state.
Device Location Info: Current location via GPS or IP
Registration & Compliance Status:
Whether the device is registered to the KC platform and registration time
Current compliance state (compliant / non-compliant)
Device Identity Info: Brand, model, serial number, device ID
OS & Patch Info: Android version, firmware version, security patch level
Network Info:
Connected Wi-Fi SSID, IP address, MAC address
SIM card info (if available): ICCID, carrier, phone number
Device Security State:
Whether PIN, ADB, or developer mode is enabled
Whether storage encryption is enabled, and if unknown sources are allowed
1.2 Applicable Scenarios
Compliance check: Quickly determine if device meets bound policy requirements
Regional identification and grouping: Use location data for geo-based device grouping and policy delivery
Asset review and management: View basic info like SN, model, firmware, etc.
Security validation: Identify risky states like ADB enabled or unknown sources
Deployment QA sampling: For operations to spot-check registration status, network configuration, and uptime
2. Applications Tab
Notes:
App data is reported periodically by the device and may be delayed
If the device is not bound to an app policy, lists like “allowed apps,” “blocked apps,” or “mandatory apps” may be empty
System apps are hidden by default; only user-installed apps are shown
2.1 Feature Overview
The "Applications" tab shows the currently installed user apps and compares them with policy-defined allow/block/mandatory apps to assist with policy verification, compliance validation, and issue diagnosis.
User App List:
Lists all currently installed user apps (excluding system apps)
Shows app name, package name, version, source of policy, and installation time
Policy-configured Apps (if policy is bound):
Allowed Apps (Whitelist): Apps allowed by policy, optional to install
Blocked Apps (Blacklist): Apps forbidden by policy; presence is a violation
Mandatory Apps: Must be installed per policy; absence = policy non-compliance
Policy Comparison Indicators:
System compares policy and actual installation to flag missing, extra, or wrong-version apps
Compliance indicators (✔ / ❌) are shown
3. Policy Tab
Notes:
Policy execution status relies on device reporting; if the device has been offline for a long time, displayed information may be outdated.
Compliance determination for some policy fields is based on field-by-field comparison and does not represent the delivery status of the entire policy.
If the policy is inherited from a group, modifications must be made in the group, and cannot be unbound individually from here.
3.1 Feature Overview
The “Policy” tab displays all currently effective policies and their execution status for this device. It also provides compliance assessment and execution history to help confirm policy source, delivery, and results.
Overview of Effective Policies
Effective Policies Overview (Left Details + Right Navigation) The left panel displays the following policy configuration blocks by type:
Device Policy
Application Distribution Policy
Application Update Policy
Kiosk Policy
File Distribution Policy
Each policy block shows basic info and configuration details including:
Policy Name and ID
Policy Type
Execution Version
Policy Delivery Time
Detailed Policy Configuration
The right side contains a quick navigation menu for switching between multiple configuration blocks.
Policy Compliance Status
Displays whether the current device status meets the requirements after policy execution.
If compliance fails, the reason will be highlighted (e.g., “App not installed”, “PIN not set”).
Associated Policies
Shows all policies currently bound to this device.
Helps identify policy sources and coverage to avoid conflicts or duplicate configurations.
Policy Delivery History
Displays all past policy delivery records in chronological order, including:
Policy Name, Type
Executed Version, Latest Version
Execution Result (Success / Failure)
Delivery Timestamp
4. Device Groups Tab
Notes:
A single device can belong to multiple groups. If groups apply the same type of policy, the platform will automatically merge them by type.
Changing group assignments may trigger system actions such as policy re-pushing or file reissuing.
When the same type of policy is inherited from multiple groups, the effective policy is a merged result.
4.1 Feature Overview
The “Device Groups” tab displays all groups that the current device is assigned to, along with the policy types mounted to each group. It supports adding or removing group associations.
Group List:
Shows all groups the device currently belongs to
Displays mounted policy types and policy names for each group
Helps identify the group inheritance structure of policies
Quick Operations:
Add to Group: Assign the device to a new group
Remove from Group: Remove the device from a current group
Group changes take effect immediately and may cause policy re-execution. Please operate with caution.
5. Device Tab
Notes:
Information in this tab is reported by the device itself. If the device is offline, some fields may be missing or outdated.
Available fields vary depending on the device model and firmware version.
Only devices recognized and managed by KC will display relevant information.
5.1 Feature Overview
The “Device” tab presents detailed hardware specifications, software version, network identifiers, and security configurations of the device. It is useful for operations, technical support, and asset management.
Device Information
Device ID
Device management mode (e.g., KMA)
Android API level
Brand / Model / Manufacturer
Serial Number
Baseband version
Network
Wi-Fi MAC address
IMEI / MEID
SIM card ICCID
Carrier Name
Phone Number
Security
Whether PIN lock is enabled
Whether ADB / developer mode is enabled
Whether installation from unknown sources is allowed
Whether encryption is enabled
Whether install protection is enabled
6. System Settings Tab
Notes:
System settings are reported periodically by the device; some configuration states only update after reboot or policy push.
If the device is not bound to a system policy or is offline, fields may show as “Not Set.”
Supported settings may vary by model and firmware version; unsupported items will be hidden.
6.1 Feature Overview
The “System Settings” tab displays the actual configuration status of the device’s system parameters. These values reflect the final result after policy delivery and allow users to confirm whether key parameters are properly controlled.
Connectivity Settings
Whether Wi-Fi is enabled
Whether mobile hotspot is enabled
Whether Bluetooth is enabled
Bluetooth name or alias (if supported)
Display & Sound
Screen brightness
Volume level
Screen timeout duration
Security & Permissions
Whether compliance detection is enabled
Whether USB debug protection is enabled
Whether Google Settings / Play Store is accessible
Whether installation from unknown sources is allowed
6.2 Policy Compliance Evaluation
By comparing actual device configuration with policy settings (refer to “Policy” tab), users can:
Check if important switches like Wi-Fi, USB Debugging, screen timeout, etc. are set correctly
Identify non-compliant values (e.g., volume not muted, Bluetooth still enabled)
Determine whether policy delivery was successful and took effect
6.3 Troubleshooting & Debugging
This tab should be used in combination with the “Policy” and “System Logs” tabs to:
Identify whether a device is not executing policy as expected
Check reasons for failure, such as device being offline or policy being overridden
Support technical teams in analyzing root causes of device misbehavior
7. Location Tab
Notes:
Location data is reported by the device client, based on GPS or IP.
Location acquisition depends on whether the location permission is enabled and whether signal/network is available. If not available, the map will appear empty.
Only the latest location is displayed here; this is not a continuous real-time tracking map.
Lost Mode enables enforced reporting and screen lock.
7.1 Function Overview
The "Location" tab shows the latest reported location of the device and supports basic location-related remote operations.
Device Location Data
Displays the device’s last known location on a map
Shows the geocoded address, coordinates, and reporting timestamp
Displays the positioning method (GPS or IP-based)
Remote Operations
Enable Lost Mode
Force the device to report location
Lock the device screen and display the Lost Mode interface
View Location History
Redirect to the [Location Trace] tab to view the historical movement path of the device
7.2 Linkage with Other Functions
Policy compliance inspection: Use with the "System Settings" tab to check whether location permission is enabled
Device operation dispatching: Assist in dispatching the nearest field technician
Risk investigation: Determine whether the device is in an abnormal geographic area or has gone offline
8. Operation Log Tab
Notes:
Only shows remote manual operations actively triggered by platform users.
Status is based on device feedback; if the device is offline, operations may remain in “executing” status.
The same operation performed on multiple devices will generate separate records for each device.
8.1 Function Overview
The “Operation Log” tab records all historical manual operations executed on the current device. It supports multi-condition filtering and log detail viewing.
Operation Log List
Each row corresponds to a single operation record and displays:
Task ID
Operation Type (e.g., Reboot, Lock Screen, Lost Mode, Reset Device, Install App, etc.)
Operator: The user who triggered the operation
Operation Time
Operation Reason (if filled in during execution)
Execution Result: Success / Failure
Log Details: Click to view specific status or error message
Filtering Options
Supports filtering by:
Operation type
Execution result (success/failure)
Operation time
Keyword search (e.g., operator name, task ID)
9. System Log Tab
Notes:
The log list is reported by the KC client app; it may not be updated if the device is offline or if logs exceed the report interval.
System logs differ from operation logs: they record device-side behaviors and are triggered by automated policy enforcement or app activity.
Some logs will only appear if the corresponding policy feature is enabled (e.g., forbidden app monitoring, kiosk exits, etc.).
9.1 Function Overview
The “System Log” tab displays behavior events automatically reported by the device agent. It provides context for compliance monitoring, debugging, and policy effectiveness validation.
Log List Structure
Each row contains one log entry with the following fields:
Log Type (e.g., App Uninstall, App Install, Forbidden App Opened, Device Reboot, Policy Executed, App Crashed)
Log Message (detailed description of the behavior)
Timestamp
App Info (if applicable): Package name, version
Policy Source (if applicable): Policy name and type
Trigger Mode: Passive (e.g., system monitoring) or active (e.g., user action)
Log Display Rules
Sorted in reverse chronological order (latest first)
Only shows logs from the current device
Max retention time and volume may be subject to platform limits