1. Features and Objectives
The Enrollment Management module is used to centrally manage the entire enrollment process of imported devices before and after accessing KiwiCloud. In the Managed and To be Managed views, administrators can set Enrollment Methods in bulk or individually, perform IMA bulk/single enrollment, and revoke configurations for managed devices. This ensures the enrollment process is efficient, controllable, and traceable.
Special Notes:
The module includes two tabs: Managed and To be Managed.
Managed allows administrators to revoke configurations from registered and controlled devices.
To be Managed supports batch setting and individual Enrollment Method configuration, as well as operations such as IMA bulk enrollment / IMA single enrollment / device deletion.
Common Enrollment Methods include: Zero-touch enrollment, QR code enrollment, Manual, and Automatic (actual availability depends on device type and enterprise configuration).
Main Operations in To be Managed Tab:
Operation | Description |
Set Enrollment Method | Assign a specific enrollment method to one or more devices. |
Batch Configuration | Apply a enrollment method to multiple devices at once to improve deployment efficiency. |
IMA Enrollment | Perform enrollment on one or more IMA devices. |
IMA Batch Enrollment | Register multiple IMA devices at once, suitable for large-scale deployments. |
Delete Device | Remove selected devices from the “To be Managed” list to clear invalid or mis-imported data. |
Main Operations in Managed Tab:
Operation | Description |
Revoke Configuration | Cancel applied configurations for devices to allow re-enrollment or policy reassignment. |
Typical Use Cases:
After importing a new batch of devices, use the To be Managed view to batch set Enrollment Methods and perform IMA bulk enrollment for quick onboarding.
When a store changes networks or policies, perform Revoke Config on Managed devices to re-register and apply the new policy.
Before delivery, system integrators can perform single device enrollment and onsite acceptance testing. Once validated, bulk enrollment can be applied.
Use Delete Device to clean up test entries or duplicate imports, ensuring the To be Managed list remains accurate.
2. To be Managed Tab
2.1 Set Enrollment Method (Single/Multiple)
Description
This function allows administrators to assign a enrollment method for devices in the "To be Managed" list. It supports single entry setting as well as batch settings (list quick setting), and applies to KMA / GMA / IMA management types.
Available Enrollment Methods:
Manual:
For KMA/GMA devices, the enrollment process must be triggered manually on the device side by tapping Register in the KC App.
For IMA devices, enrollment must be initiated from the KiwiCloud console using IMA Enrollment or IMA Batch Enrollment.
Auto:
For KMA/GMA devices, enrollment is automatically triggered by the KC App once the device is connected to the internet, with no manual intervention required.
For IMA devices, the enrollment process is automatically completed upon device activation, without requiring manual actions.
Notes
Only applies to devices under To be Managed; already managed devices cannot be modified.
Batch setting is a list quick function: after selecting multiple devices, use the dropdown Select Enrollment Method at the top of the list to apply in bulk.
For IMA devices:
If the Enrollment Method is set to Automatic, the device will complete enrollment automatically upon activation.
Once successful, the device will automatically move into Managed status and be marked as In Use, without requiring IMA Enrollment / IMA Batch Enrollment.
The Enrollment Method only defines how enrollment is triggered; it does not change the management type (KMA/GMA/IMA).
Steps
Single Setting
Locate the target device in the "To be Managed" list;
In the Enrollment Method dropdown of the corresponding row, select Manual or Auto;
The system saves the setting instantly and updates the list with the new result.
Batch Setting (List Quick Setting)
Select multiple devices to configure;
At the top of the list, click the Please select an enrollment method dropdown, then choose Manual or Auto;
The system applies the chosen Enrollment Method to all selected devices at once.
2.2 Batch Configuration
Description
The Batch Configuration function allows administrators to import multiple devices either by entering SNs or uploading a template, then assign a Enrollment Method in bulk and submit at once. This is designed for large-scale deployments or remote imports, and applies to KMA / GMA / IMA devices.
Notes
Supported file formats: xls/xlsx, maximum file size ≤ 5MB. After import, the system validates format and SNs; only “validated successfully” SNs will be added to the list.
The popup allows Select All / Deselect All via the header checkbox; changes take effect immediately upon submission.
For IMA devices: If the Enrollment Method is set to Automatic, the device will complete enrollment automatically upon activation, without requiring IMA Enrollment or IMA Batch Enrollment. Once successful, devices move to Managed and status updates to In Use.
Manual/Automatic only determines the enrollment trigger method; it does not change the device management type (KMA/GMA/IMA).
Steps
A. Entering SNs
Click the Batch Configuration button at the top to open the popup.
Paste multiple SNs into the SN Input Box (separated by commas, spaces, or line breaks).
Click Add Device; the system validates the SNs and displays a Validation Results popup with Success/Failure tabs.
Return to the Batch Configuration popup:
Use the header checkbox to select all if needed.
Expand Batch Set Enrollment Method at the bottom, and choose Automatic or Manual.
Click Submit; the settings take effect in bulk, and the updated results are displayed in the “To be Managed” list.
B. Template Import
In the Batch Configuration popup, click Download Template to get the Excel file
ImportDeviceTemplate.xlsx.
Fill in the SN column line by line, then save the file.
Drag the file to the Upload Area on the right, or click to upload (xls/xlsx, ≤ 5MB).
The system displays Validation Results with Success/Failure tabs. If there are failures, correct and re-upload as prompted.
Return to the Batch Configuration popup; select the target devices or use Select All via the header checkbox.
At the bottom, choose Automatic or Manual under Batch Set Enrollment Method.
Click Submit to apply settings, then return to the “To be Managed” list to view the results.
2.3 IMA Enrollment
Description
This function is used to initiate background enrollment for devices under the IMA management mode directly from the console. It is only applicable when the IMA device’s Enrollment Method is set to “Manual.” If the IMA device’s Enrollment Method is set to Auto, the system will automatically complete the enrollment and move the device to Managed (status: In Use) without needing to click this function.
Notes
Applicable only to devices under IMA management mode. KMA/GMA devices do not support this function.
The default Enrollment Method of IMA devices may be “Manual.” Administrators can adjust it to “Automatic” using the 2.1 / 2.2 operations.
If successful: the device will move to Managed with status In Use.
If failed: check whether the device is indeed IMA, the SN validity, and whether the device is connected to Ali IoT.
Steps
Select Device: Go to Enrollment Management → To be Managed, visually identify devices with Control Methods = IMA, and select the target devices.
Initiate Enrollment: Click the toolbar button [IMA Enrollment].
View Result: After successful enrollment, the device will move to “Managed” with Device Status = In Use. If it fails, check whether the device has completed IMA marking, the SN is valid, and whether it has been connected to Ali IoT.
2.4 IMA Batch Enrollment
Description
This function is used to perform bulk background enrollment for devices under the IMA management mode. It is only applicable when these IMA devices are set to “Manual” enrollment. Two import methods are supported: Enter SN and Template Import SN. If the imported IMA devices are already set to Automatic, they will automatically complete enrollment upon connecting to the network, and there is no need to submit this bulk enrollment.
Template import supports xls/xlsx only, with a maximum file size of ≤5MB. The system performs validation first, and only SNs that pass validation will be added to the pending enrollment list.
This feature is only available for IMA devices. Once submitted, the system will process immediately.
After bulk submission, successfully registered devices will automatically move to Managed with status In Use.
Steps
A. Batch Enrollment via Enter SN
Go to Enrollment Management → To be Managed, click [IMA Batch Enrollment] to open the popup.
In the left SN input box, paste multiple SNs (supports comma, space, or line break), then click [Add Devices].
Check the “Batch Import Validation Result”, then return to the popup to confirm the list.
Click [Batch Enrollment] to initiate enrollment. Once successful, the devices will move to Managed with status = In Use.
B. Batch Enrollment via Template Import
In the popup, click [Download Template] to get the Excel template ImportDeviceTemplate.xlsx, fill in device serial numbers (SN) in the SN column row by row, and save.
Drag the file into the Upload Area on the right or click to upload (supports xls/xlsx, ≤5MB). The system will complete validation and display the results.
After confirming the list, click [Batch Enrollment] to proceed with batch enrollment. Once successful, the devices will move to Managed with status = In Use.
3. Managed Tab
3.1 Revoke Configuration
Description
Revoke Configuration is used to remove device control from its current managed state, with options to erase data and set the device’s subsequent status as required. This is commonly applied when a device is retired, decommissioned, sent for repair, or redeployed. The operation is executed on a single device within the Managed tab.
Two modes:
Mode 1: Erase Device Data
Executes a factory reset, erasing local storage;
Sets device status to:
Unregistered: The record remains, allowing future re-initialization and enrollment;
Retired: Indicates permanent deactivation or disposal; the device will no longer be part of enrollment or management.
Mode 2: Do Not Erase Device Data
Keeps local data intact;
Sets device status to Maintenance, indicating the device remains usable but its configuration is reset;
The platform automatically applies the default policy to ensure the device remains under minimal control.
Notes
Factory reset requires the device to be online; if offline, the operation will fail.
Retired is a permanent deactivation status; the device cannot be registered again, use with caution.
Data erased by a factory reset is irrecoverable; select “Do not erase” if data retention is required.
Devices in Unregistered status remain listed in the platform and can be re-registered later.
Maintenance is suitable for repairs, diagnostics, or temporary deactivation; the system will push a default policy to keep the device minimally managed.
Steps
Select the Target Device
In the “Managed” list, locate the device and click [Revoke Configuration].
Set Revoke Options
Erase Device Data: Choose “Yes / No”;
Target Status:
If “Erase”: set to Unregistered / Retired (optionally check “Delete Device” to remove from platform records);
If “Do not erase”: set to Maintenance (the system will push a default policy automatically).
Provide Reason
Enter a brief description of the reason in the “Operation Note/Reason” field for audit tracking (required).
Submit and Confirm
After clicking [Revoke Configuration], the system will display a confirmation dialog; once confirmed, the operation takes effect immediately.
After execution, the device status is updated to the chosen target state and displayed accordingly in the list.
4. Enrollment Process Overview
This chapter explains the key configuration items of Enrollment Management and provides the complete enrollment process for KMA / GMA / IMA devices.
4.1 Preparation Before Enrollment
Item | Description |
Device Source | iMin production devices: automatically synced from the iMin system to KiwiCloud, no manual import required. Non-iMin or test devices: must be imported first via “Enrollment → Device Import” before they can be registered. |
Basic Requirements | Device must be network-ready; SN must be unique and identifiable; KC App (or Google ADP / iMinkit) must be pre-installed per device type and launchable. |
Enrollment Mode | Configurable as Manual or Automatic: - Manual: For KMA/GMA devices, enrollment must be triggered manually by tapping [Register] in the KC App; for IMA devices, enrollment must be triggered in the KiwiCloud console via [IMA Register] or [IMA Bulk Register]. - Auto: For KMA/GMA devices, once connected to a network, the KC App will automatically trigger enrollment; for IMA devices, enrollment completes automatically upon device activation without manual intervention. |
4.2 KMA Enrollment Process
Applicable: Devices certified and tested with the KiwiCloud App.
Trigger: KC App (manual or automatic, depending on the enrollment mode).
Process:
KC App launches. If “Unregistered,” it first reports Manufacturer / Model / SN.
Console returns the enrollment mode (manual/automatic).
If automatic: KC App immediately initiates enrollment. If manual: user must tap [Register] on the device.
During initiation, the App reports whether an ADP package exists.
Backend determines: No ADP → KMA enrollment.
Backend matches first with over-quota records (if found, update record); if not, matches unregistered records (if found, update).
If neither is found: KMA returns an error and enrollment fails (requires checking import/quota data).
On success, device moves to Managed / In Use.
4.3 GMA Enrollment Process
Applicable: GMS-certified devices, factory reset, registered via Google Zero-touch or QR Code.
Trigger: Enrollment initiated by Google Zero-touch / QR Code → KC App continues the process with reporting and enrollment.
Process:
Enrollment initiated via Google Zero-touch / QR Code.
KC App starts, detects “Unregistered,” and reports Manufacturer / Model / SN and ADP package presence.
Console returns enrollment mode (manual/automatic) and identifies device as GMA managed.
KC App triggers accordingly: Automatic = registers directly, Manual = user must tap [Register].
Backend matches first with over-quota records, then unregistered records, and updates accordingly.
If no match: GMA creates new data for the device and registers it successfully.
On success, device moves to Managed / In Use.
4.4 IMA Enrollment Process
Applicable: iMin models (below Android 13), managed through iMinkit + KC in the IMA control flow.
Trigger: Device activates and connects to Alibaba IoT, then system automatically marks it as IMA.
Default Marking:
iMinkit calls KC APIs to mark the device as IMA managed in KC. Enrollment mode is usually manual, but can be changed to automatic via the console (Sections 2.1/2.2).
Two Trigger Modes:
Automatic: If enrollment mode = automatic, the IMA device auto-registers upon network connection, without requiring IMA Register / IMA Bulk Register. Device is then directly marked as Managed / In Use.
Manual: If enrollment mode = manual, admins must use [IMA Register] / [IMA Bulk Register] in the “To be Managed” list to trigger backend enrollment.
Backend Handling:
Backend processes using the same sequence: over-quota → unregistered. Once complete, device status = In Use.