This article introduces the three KiwiCloud device management modes (IMA, KMA, and GMA) and explains how to enroll devices under each mode.
1) Mode Overview
IMA (iMinKit Managed Access): Continuation of iMinkit-style management. Devices are managed via the legacy IoT interface and no KCAPP installation is required.
KMA (KiwiCloud Managed Access): KiwiCloud native policy-based management with richer app/policy enforcement capabilities. In most cases, enrollment and management are completed with KCAPP.
GMA (Google Managed Access): Managed through Google’s official framework (AMAPI) using Android Enterprise.
2) IMA vs KMA vs GMA Comparison
Dimension | IMA | KMA | GMA |
Management approach | Continuation of iMinkit-style management | KiwiCloud native policy-based management | Google official management framework |
Policy & configuration experience | Depends on device online status | Policies remain effective; devices sync automatically once online | Policies are synced via Google services |
Device offline impact | Supports up to 14 days offline | Long-term offline supported | Long-term offline supported |
Suitability for offline device management | Not suitable for offline device management | Not suitable for offline device management | Not suitable for offline device management |
App install & update experience | Updates may be delayed; reboot required in some cases | Near real-time updates when online, with global acceleration | Fast updates when online, dependent on Google services |
Supported enrollment methods | Zero-touch configuration, manual enrollment | Zero-touch enrollment, QR / enrollment-code enrollment (some devices also support in-app “Register” / auto registration in KCAPP) | Zero-touch enrollment, QR enrollment |
Grouping & scale management | Multi-group, auto-grouping supported | Multi-group, auto-grouping supported | Multi-group, auto-grouping supported |
App management scope | KiwiCloud public apps only | Public apps / Private apps / Web apps | Google public apps / Private apps / Web apps |
App control capabilities | Basic | App pre-configuration, permission control, rollout status | App pre-configuration, permission control, rollout status |
3) Device Type & Mode Availability
3.1 iMin device version rules
iMin devices that are GMS-certified: support GMA mode.
iMin devices below Android 14: support IMA mode.
iMin devices on Android 14 or above: support KMA mode.
3.2 Other device reference
GMS-certified devices (Android 11 and above): support GMA for cross-brand management.
Non-GMS devices (non-iMin): do not support GMA. KMA is available, but the device must integrate KC SDK and have KCAPP pre-installed.
4) Enrollment Methods & Prerequisites
4.1 GMA (Google Managed Access)
4.1.1 QR Enrollment
Prerequisites
A registered Android Enterprise account is required.
Authorize the Android Enterprise account in System Management > Android Enterprise.
In KiwiCloud Console, create a GMA Enrollment QR Code.
Devices enrolled via QR: no device import is required.
Steps
Power on the device (new or factory reset).
On the welcome screen, tap 6 times to enter the QR code scanning interface.
Scan the Enrollment QR code to complete enrollment.
After enrollment
The device is managed using Google’s Android Management API (AMAPI).
The system automatically installs the ADP software.
The KiwiCloud App (KCAPP) will be installed by default.
4.1.2 Zero-touch Enrollment
Prerequisites
A registered Android Enterprise account is required.
Authorize the Android Enterprise account in System Management > Android Enterprise.
In KiwiCloud Console:
Bind the Google Zero-touch portal
Create a Zero-touch Configuration
Import devices and bind them to the Zero-touch Configuration
Steps
Power on the device (new or factory reset).
The device will enroll automatically and apply the bound Zero-touch configuration.
4.2 KMA (KiwiCloud Managed Access)
4.2.1 QR / Enrollment-code Enrollment
Applies to
Devices enrolled via QR/enrollment-code: no import into the KC management console is required.
The device must have KCAPP pre-installed (e.g., pre-installed in ROM or factory pre-installed).
Create a KMA enrollment QR code (or generate an enrollment code) in KiwiCloud Console.
Steps
Power on the device and open KCAPP.
In KCAPP, choose one of the following:
Scan the QR code, or
Enter the enrollment code
Complete enrollment and the device will apply the organization’s policies and configurations.
4.2.2 Zero-touch Enrollment
Prerequisites
A KC system admin assigns Zero-touch devices to the enterprise.
The enterprise creates a KMA Zero-touch configuration in KiwiCloud Console and binds devices to the configuration.
Steps
Power on the device (new or factory reset).
The device will enroll automatically and apply the bound configuration.
4.2.3 Legacy KCAPP enrollment flow (for some older devices)
Some older devices with KCAPP pre-installed still support the legacy enrollment flow inside KCAPP (e.g., tap Register or use Auto registration) to complete enrollment.
4.3 IMA (iMinKit Managed Access)
4.3.1 Zero-touch configuration enrollment (unactivated IMA devices)
For IMA devices that have never been activated, you can create a zero-touch configuration to enable:
Automatic group assignment
Automatic policy creation
Automatic enrollment into KiwiCloud
4.3.2 Manual enrollment (activated IMA devices)
Steps
An iMin Admin syncs device ownership from the iMin-KC system to KiwiCloud. Devices appear under Device Registration > Pending Management in an inactive state.
The iMin Admin manually or batch registers the devices.
Once registered, Institution Admins can manage the devices.
Notes
No KCAPP installation is required; devices are managed via the legacy IoT interface.
Older iMin devices with updated ROM + KC SDK can be upgraded to support KMA management.