1. Function & Application Objectives
The Device Grouping module enables logical grouping and centralized management of terminal devices. Users can classify devices into groups based on store, region, organizational structure, or business scenarios. This facilitates structured classification, centralized policy delivery, and remote maintenance. It serves as a key hub connecting core capabilities like Device Management, Policy Management, and Remote Operations.
Important Notes:
Groups are created without any policies by default;
Whether grouping a device affects its current policy depends on whether the group policy is selected for delivery;
Policies must be explicitly bound via the Associate Policy operation;
A device can belong to multiple groups simultaneously;
Group-level policies take precedence over device-level policies; effective policies follow a layered stacking logic;
At any given time, a device can only be in either Whitelist or Blacklist application control mode—not both.
Key Operations
The following key operations are supported in the Device Grouping module:
Operation | Description |
Create Group | Create a new device group and add available devices. No policy is associated during creation, and existing policies remain unchanged. |
Add Device | Add one or more devices to the selected group(s). If the group has bound policies, those will apply according to delivery options. |
Modify | Edit group name, description, and member devices. Devices and policy delivery can be adjusted without affecting existing active policies. |
Delete | Delete a single group, removing its associated policies and configurations. Triggers re-evaluation of device policy stack. Non-reversible. |
Delete Groups (Bulk) | Delete multiple groups at once. Logic is the same as "Delete". |
Associate Device Policy | Bind one device policy to selected devices. Policy takes effect through stacked configuration, supporting GMA, KMA, and IMA device types. One policy per device per type. |
Associate App Policy | Bind one application policy to selected devices. Follows stacking logic and applies to GMA / KMA / IMA device types. |
Associate File Policy | Associate one or more file distribution policies to selected devices for remote file delivery. Files are deduplicated across policies. |
Clear App Data | Send commands to selected devices to clear local app data, restoring to the initial install state. Only supported for GMA devices. |
Remote Reboot | Send reboot command to selected devices (only effective when online). GMA supports retry within 10 minutes; KMA/IMA do not. |
Group Details | View detailed information on group members, policies, applications, and logs. |
Typical Application Scenarios
Grouping devices by region, store, or project for structured management;
Batch delivery of unified policies to similar devices;
Coordinate with the Remote Operations module to reboot, lock, or wipe data by group;
Operations teams conduct batch maintenance based on policy logs and device statuses;
Quickly assign newly registered devices to groups for standardized naming and policy enforcement.
2. Primary Operations
2.1 Create Group
Description
The Create Group operation is used to establish a new logical device group for unified policy configuration and batch operations. Users can define the group name and description, and select currently available devices to add to the group.
Steps
Click "Create Group" Button Access the group creation interface.
Enter Basic Information
Group Name: Required. Used to identify the device group;
Group Description: Optional. Can include notes on the group's purpose or scope.
Select Devices
Devices can be filtered by "Device Name", "Serial Number", etc.;
The list displays all devices currently eligible to join the group, with multi-select support;
Device info includes: Name, Model/Manufacturer, Serial Number, etc.
Submit Creation
After confirming the information and selected devices, click Submit to complete creation;
The new group will appear in the main “Device Group” list.
Notes
Only devices that are registered and available can be added to a newly created group;
Creating a group will not activate any policies or trigger remote operations;
To push policies to the group later, use the Associate Policy functions in the “Operations” menu;
A single device can be added to multiple groups without conflict.
2.2 Delete Group
Description
The Delete Group operation is used to remove one or more unused device groups. The system will delete the selected group(s) and their device associations. If any type of strategy (Device, Application, or File Distribution) is linked to the group, those strategies will be unbound from the associated devices. The system will then re-stack and reapply effective strategies to those devices.
Steps
In the "Device Groups" main page, select one or more groups;
Click the Delete Group button in the top toolbar;
A confirmation dialog will appear, explaining the strategy unbinding and potential device impacts;
Upon confirmation, the system will:
Delete the selected groups;
Remove group-to-device assignments;
Remove the effects of the group’s strategies from associated devices;
Re-stack and reapply remaining strategies on affected devices.
Notes
This operation is irreversible. Please ensure that group-level strategies are no longer needed;
Deleting a group does not delete the devices themselves;
The effect of the group's strategies is removed immediately upon deletion;
Strategy changes caused by group deletion can be tracked in Device Detail or via System Logs;
Deleting a group does not delete the strategies themselves, only their device associations.
2.3 Add Devices
Description
This operation allows registered and available devices to be added to a specific device group, with an optional setting to apply the group’s currently active strategies to the newly added devices.
Each device group can be linked to various strategies (e.g., Device Strategy, Application Strategy, File Distribution Strategy). During the add process, the system automatically identifies the device type (GMA/KMA) and displays the group’s currently active strategies for that type, allowing users to flexibly control the delivery behavior.
Steps
Open the Add Devices Page
Navigate to the target group’s detail page;
Click the Add Device button in the top right corner to enter the operation page.
Filter Target Devices
The page displays all available devices (i.e., registered and in "In Use" status);
Select the devices to be added to the group.
Confirm Strategy Selection
The lower section of the page categorizes the group’s currently active strategies by device type (GMA / KMA);
Options:
Select strategy(ies): The new devices will be bound to and immediately receive the selected strategy(ies);
Deselect strategy(ies): The strategy binding will be established, but will not be immediately applied.
Submit the Operation
Click Add to Group to complete the action;
Based on your selection, the system will bind the strategies and determine whether to push them immediately.
Notes
Adding new devices does not affect the existing devices or their current strategy status in the group;
Once added, devices participate in the group strategy stacking mechanism—future updates to the group strategy will apply to all bound devices;
If devices already have other strategies, the new group strategy will be stacked with them. You can review the composite strategy in Device Detail – Effective Strategies Overview;
Strategy delivery is device-type specific: GMA strategies apply only to GMA devices, KMA likewise;
Unselected strategies are only bound to the device, allowing for future batch delivery or scheduled rollout;
We recommend choosing the delivery method based on specific scenarios to avoid configuration conflicts.
2.4 Edit
Description
This operation allows users to edit the basic information and member device list of a group. You can modify the group name, description, and adjust the list of added devices (add/remove devices), as well as configure strategy delivery behavior.
This operation does not affect the currently associated strategies or configuration status. Changes only take effect when the user actively updates the device list or modifies the strategy selection.
Steps
Click More > Edit in the device group list to open the edit page;
Enter a new Group Name (required) and Group Description (optional) at the top of the page;
Use filters (device name / serial number) to select available devices; checked devices will be added to the group;
At the bottom of the page, GMA / KMA strategy sections are displayed—checking a strategy means it will be immediately pushed to newly added devices of the corresponding type; if not checked, the strategy will only be bound (not pushed);
Click Save to apply and update the group configuration.
Notes
Group names must be unique—no duplicates are allowed;
Editing will not impact previously applied strategy configurations; only new devices or changes will take effect;
Groups can be edited multiple times. All changes are logged and available for audit review.
2.5 Delete
Description
This operation is used to delete an individual device group directly from the Group List page. Upon deletion, all configurations—including strategy, application, and other bindings—between the group and its devices will be automatically removed. The system will re-evaluate and re-stack the affected device strategies to ensure the latest configurations take effect immediately.
This operation is functionally identical to batch deletion; the only difference lies in the entry point.
Steps
Access Group List
Open the “Device Groups” module and view the list of available groups;
Click Action Button
In the row of the target group, click Actions → Delete;
Confirm Action
A system prompt will appear: “Deleting this group will remove all strategies, applications, and configurations applied to its devices.”
Click Confirm to proceed, or Cancel to abort;
System Processing
The selected group will be deleted;
All strategy bindings between the group and its devices will be removed;
The system will automatically re-stack the remaining strategies for affected devices;
View Results
Once successful, the group will be removed from the list;
You can check updated device strategies via Device Details → Effective Strategy Overview.
Notes
Deleting a group will remove all associated group-level strategies from its devices;
All strategies follow a stacking mechanism, and group-level strategies take precedence over device-level strategies;
After deletion, the system will re-evaluate and apply effective strategies for each device;
This operation cannot be undone, proceed with caution;
All deletions are logged in the system logs for auditing.
2.6 Associate Device Policy
Description
This operation is used to associate the selected devices with a specific device policy, enabling unified management of device behavior control, system configurations, and feature restrictions.
Device policies support both GMA and KMA device types. The platform will automatically group devices by type, and users must select a policy for each type under the corresponding tab.
All policies are applied using a stacking structure: if a device already has other policies, the new policy's configuration fields will override any overlapping fields in the previous policies to form the final effective configuration. Device-level policies have lower priority than group policies—if there is a conflict, group policies will take precedence.
Steps
Select Devices
In the device group or device list, check the target devices and click Associate Device Policy;
The system will automatically detect the device types and categorize them under GMA and KMA tabs;
Review Device List
Each tab displays the selected devices' name, model/manufacturer, and serial number for confirmation;
Select Policy
The policy list in each tab includes policy name, policy ID, and latest version;
You can select only one policy per device type tab;
Submit Operation
Click Save to confirm. The policy will be immediately associated and pushed to the devices;
You can view associated policies and delivery history under Device Group Details → Policy tab;
You can also check actual effective policies in Device Details → Policy tab.
Notes
This operation allows associating only one policy per device type (GMA or KMA) at a time;
If a device is governed by multiple policies, the latest associated policy's configuration fields will override earlier ones;
When multiple devices are selected, the system will merge and stack configurations for each device individually;
If a device is offline, the policy will take effect once it reconnects;
If a device is also bound to a group policy, the group policy takes precedence over directly associated policies with overlapping fields.
2.7 Associate Application Policy
Description
This operation allows manually assigning an application policy to one or more devices, enabling control over app installation, distribution, and runtime behaviors—such as allow/block lists, silent installation, and auto-start settings.
The interface automatically separates devices into GMA and KMA (including IMA) tabs based on device type. Users must select one policy per device type. Application policies are applied using a stacking mechanism—later-delivered policies override earlier ones for the same configuration fields.
Steps
Select Devices
In the device list or device group, check the target devices;
Click Associate Application Policy to enter the operation page;
The system will automatically categorize devices into GMA and KMA tabs;
KMA policies apply to both KMA and IMA device types;
Confirm Device Information
Each tab displays the selected devices' name, model/manufacturer, and serial number;
Paging is supported for large device sets;
Select Application Policy
A list of available application policies will be shown, including: policy name, ID, and latest version;
You can select only one policy per device type;
Submit Operation
Click Save to trigger policy delivery;
If a device is offline, the policy will sync automatically upon reconnection;
You can view the associated policies and delivery history under Device Group Details → Policy;
Device-level policy application status and results can be found in Device Details.
Notes
GMA devices only support GMA application policies; KMA and IMA devices use KMA application policies;
Only one policy can be selected per device type per operation;
Policies are stacked in the order they are delivered—later ones override previous values for overlapping items;
If a device is already subject to a group-level policy, the group policy takes precedence over directly bound device policies;
After delivery, compliance status, execution results, and applied policy details can be viewed on the device details page.
2.8 Associate File Distribution Policy
Description
This operation allows you to distribute platform-configured files (e.g., configuration files, image assets) to one or more devices.
Users may select one or more file distribution policies to be delivered. Files within the selected policies will be dispatched to the device's designated path. The system automatically deduplicates files by content to avoid repeated transfers.
This feature is applicable to all device types, including GMA, KMA, and IMA.
Steps
Select Devices
In the device list or device group, check the target devices;
Click Associate File Distribution Policy to enter the operation page;
Selected devices will be displayed at the top of the page with device name, model/manufacturer, and serial number;
Select File Policies
The bottom section of the page shows all available file distribution policies;
Each policy includes: policy name, policy ID, and latest version;
Multiple policies can be selected;
Submit Operation
Click Save to deliver the policy files to the corresponding devices;
If a device is offline, the delivery will execute automatically upon reconnection;
You can view associated policies and delivery history under Device Group Details → Policy;
Policy delivery status and execution results can be checked under Device Details → Policy;
Notes
File distribution policies are universal and apply to all device types;
Multiple policies can be selected at once without conflicts;
Duplicate files (identical content across policies) will not be delivered more than once;
If a policy is updated, the device must receive the updated version via re-delivery;
File download paths and execution behavior are defined by the policy—no manual interaction is required on the device;
File distribution policies do not support stacking logic; each selected policy is executed independently and completely.
2.9 Remote Reboot
Description
This operation allows administrators to remotely reboot devices at the system level. It is commonly used to resolve system abnormalities, enforce policies, or clear network lag. The operation supports batch execution and is suitable for routine maintenance scenarios.
After the command is issued, it will only take effect if the device is online. If the device is offline, the platform handles the reboot request differently depending on the device type:
GMA Devices: The reboot command is retained in the background for a limited time (default: 10 minutes). If the device comes online during this window, the command will be executed automatically. If not, the command will expire and be discarded.
KMA / IMA Devices: These require the device to be online at the time of command issuance. They do not support command retention or delayed delivery.
Steps
Select Devices
From the device list, device group, or device detail page, select one or more target devices;
Click the Remote Reboot button to open the operation dialog;
Enter Operation Reason
The system will display a prompt stating that the reboot will interrupt any ongoing user activity, and if the device is password-protected, manual unlocking will be required after reboot;
Enter the reason for this operation (required);
Submit Operation
Click the Remote Reboot button;
The command will be sent to the selected devices, and those that meet the criteria will respond immediately;
View Execution Results
Navigate to Device Details → Operation Logs to review the status and any failure reasons of each operation.
Notes
All device types must be online for the reboot command to take effect;
GMA devices support a 10-minute validity window for reboot commands; if the device comes online within this period, it will reboot automatically. After that, the command expires;
KMA / IMA devices do not support delayed execution—the device must be online at the time of sending;
If the device has a lock screen password, it must be manually entered after reboot;
Devices in Lost Mode, Kiosk Mode, or Locked Status will continue to enforce their current policies after reboot;
Operation reasons will be recorded in the platform's operation logs. It's recommended to fill them out properly for audit tracing.
2.10 Clear App Data
Description
This operation is used to reset the usage state of an installed application on the device, clearing all app data while retaining the installation package (i.e., the app is not uninstalled).
It is suitable for scenarios such as abnormal app behavior, clearing user information, or resetting before initialization. The system supports batch operations on multiple devices and automatically filters out non-GMA devices (e.g., KMA, IMA).
Steps
Select Target Devices or Groups
From the device list, select one or more devices; or from the device group page, select one or more groups;
Click the Clear App Data button to open the operation dialog;
Select Target App
Choose the app for which you want to clear data from the dropdown menu;
Enter Operation Reason
To support auditing, a reason for this operation must be provided;
Confirm Operation
Click Clear App Data to submit;
The system will automatically exclude non-GMA devices and send the command only to eligible devices.
Notes
Only GMA devices are supported. KMA/IMA devices will be automatically excluded;
This operation is irreversible once executed—please confirm carefully;
Devices must be online to receive and execute the clear data command;
After clearing, the app will reset to its post-installation state (e.g., initial login, onboarding screens);
If the app does not properly implement data sandboxing, the reset effect may vary.
2.11 Group Details
Description
The Group Details page provides management insights for a device group, including associated devices, linked policies, whitelisted/blacklisted apps, and operation/system logs. The page supports basic filtering and pagination and serves as a key entry point for understanding group status, troubleshooting policy issues, and performing audits.
Tab Overview
1) Devices Tab
Displays all devices currently assigned to the group.
Fields displayed: Device name, model/manufacturer, serial number, OS version, online status;
Devices can be selected for batch operations (e.g., remove from group, transfer to another group);
Online status shows “Online” or “Offline”.
2) Policies Tab
Displays all policies currently associated with the group and their distribution history.
Linked Policies: Shows policy name, type, version, operator, and deployment actions;
Policy Deployment History: Lists all distributed versions and their status;
Allows manual re-deployment of policies to devices in the group;
Supports device policies, application policies, and file distribution policies.
3) Whitelist / Blacklist Apps Tabs
Displays the result of application control policies applied to devices in the group.
Fields include: App name, version, package name, policy name;
Whitelist Mode: Only apps defined in the policy are allowed to run;
Blacklist Mode: Apps defined in the policy are restricted from running;
A device can only be in either whitelist or blacklist mode at a time, not both simultaneously.
4) Operation Logs Tab
Displays remote operation records for all devices in the group.
Fields include: Operation ID, operation type, operator, reason, execution result, log details;
Supports filtering by operation type, operator, and time;
Primarily used for auditing and tracking device operations.
5) System Logs Tab
Logs automatic system actions on devices or policies, useful for backend issue analysis.
Fields include: Operation ID, action type, result, log content, duration, timestamp;
Supports filtering by log type or time range for focused diagnostics.
3. Field Descriptions
This section explains the meaning and function of each column in the Device Groups list view to help users quickly understand group status and perform management actions.
Field Name | Description |
Group Name | Custom name of the group. Clicking the name navigates directly to the group details page. |
Device Count | Total number of devices in the group (all device types are included). |
Linked Policies | Number of policies bound to the group, including device, application, and file distribution policies. |
Required Apps | Total number of apps marked as "Required" across all linked application policies (deduplicated). |
Whitelisted Apps | Number of apps defined under Whitelist mode in all linked application policies (deduplicated). |
Blacklisted Apps | Number of apps defined under Blacklist mode in all linked application policies (deduplicated). |
Non-compliant Devices | Number of devices in the group that are marked as "Non-compliant" or have failed to apply policies. |
Operator | User account that created or most recently modified the group. |
Additional Notes:
A group may be linked to multiple device, application, and file distribution policies. Counts are based on all combined policies.
Whitelist and Blacklist modes are mutually exclusive: a device can only have one mode active at a time.
Counts for Required, Whitelisted, and Blacklisted apps only reflect group-level policies, not device-level policies.