Skip to main content

IMA Quick Start

Updated over 3 weeks ago

IMA Quick Start

Note: This guide is only applicable to IMA devices — iMin devices running Android 13 or earlier

Pre-Setup Requirements for This Guide

Your KiwiCloud enterprise account has been created and the subscription license has been authorized by the KiwiCloud team.

DO NOT import the devices into KiwiCloud console, contact iMin CSE/FAE to perform the device import on your behalf.

The Serial Number (SN) of the device you will be operating should already been imported into your enterprise account and can be found under [Enrollment] → [Enrollment Management] → [To be Managed].

The following content is referenced with the IMA equipment

  • The IMA management mode currently supports only iMin Technology-branded devices (Android 13 and earlier).

  • Devices that have passed GMS Certification and support IMA can be switched to GMA mode.

  • GMA mode provides additional advanced capabilities compared to IMA, including but not limited to:

    • Password Settings

    • Auto Compliance

    • Wifi Settings

    • System Update Policy

    • OTA Annual Freeze Period

1. System Initialization

Note: After the account is created, the system will send the KiwiCloud Console URL, login account, and password to the account holder's email.

  1. Open a browser and enter the KiwiCloud platform URL.

  2. Enter the account username and password, then click the Login button.

1.1: Configure the Default Policy (Optional)

Navigate to: ☰ System Management > ☰ System Settings > 📑 Default Device Policy > 📑 Default KMA Device Policy.

Note: IMA adopts KMA’s default device policy. No standalone default policy is maintained for IMA.

  1. Modify the Password, Restrictions, and Wi-Fi policy settings as needed. For example: ➊ Disable Hotspot and Network Sharing, ➋ Set screen timeout to 30 seconds.

  2. Click the Save button at the bottom to save—changes will take effect immediately.

Additional Info: For devices managed via IMA control, once they complete the enrollment process, the "Default KMA Device Policy" configured here will be automatically applied to those newly enrolled devices.

2. Enroll Device (IMA Enrollment)

Note: Before Enrollment

  • Power on the device and connect it to Wi-Fi.

  • In KiwiCloud, you should see IMA listed under Control Methods and the Enroll button visible.

  • Don’t see the Enroll button? The device likely hasn’t been powered on before. Turn it on—after it automatically connects to the cloud, the Enroll button will appear.

2.1 Enrollment

After the admin imports the device(s) into KiwiCloud, you can enroll them in IMA using one of the two methods:

  1. Manual Registration

    • On KiwiCloud console, Enrollment Management > To Be Managed, select the device (by checking the box) and select IMA Enrollment.

  2. Bulk Registration

    • On KiwiCloud console, Enrollment Management > To Be Managed, select the devices (by checking the boxes) and select IMA Batch Enrollment.

(Optional) Verify the device was enrolled successfully. In the KiwiCloud UEM console, navigate to ☰ Enrollment > ☰Device Enrollment Info > 📑 Managed, and search for the device’s Serial Number. If the SN is found, it confirms the device has completed enrollment.

If the SN record cannot be found, please contact the enterprise administrator or the KiwiCloud support team.

3. Device Group Management (Optional)

3.1: Create a Group

  1. Navigate to: ☰ Device Management > ☰ Device Grouping.

  2. Click the Create Device Group button. Then ➊ Enter a group name (e.g., "Singapore"), ➋ Select the devices to include in this group, ➌ Click Submit to create the device group.

4. Recommended Process for Initial Business Configuration

4.1 Configure Device Policy

Step 1: Configure and Deploy a Device Policy

  1. Navigate to: ☰ Device Management > ☰ Device Policies.

  2. Create and publish a policy. Click the Create Policy → KMA Policy button (IMA adopts KMA’s policy):

2.1 Enter a policy name (e.g., "Singapore KMA Device Policy") and click the Next Step button.

2.2 Configure the device policy. For example, under the System Settings tab: ➊ Disable "Bluetooth", then ➋ Click the Next Step button.

2.3 Associate devices/groups. Under the Device Grouping tab, ➊ Find and select a group, then ➋ Click the Save and Publish button to deploy the policy.

Step 2: Verify the Policy Deployment Result (Optional)

  1. Console verification: Find the device policy "Singapore KMA Device Policy" that was just published, click the Detailsbuttonto open the policy details page. Click the Operation Log 📑 tab to check the deployment status.

  2. Device-side verification method: Pull down the Android notification panel and check whether Bluetooth has been disabled. If the policy was applied successfully, under the Bluetooth setting it will show “Not allowed by your organization”.

Image for illustration only

4.2 Add Application

There are two app types—Public and Private—and each has its own procedure for adding applications.

Which should I choose?

  • Public: Use this if the app needs to be shared across multiple organizations.

  • Private: Use this if the app is for a single enterprise. If your app doesn’t require cross-enterprise sharing, publish it as a KC Private app.

4.2.1 Public Apps

Initiate the adding of public apps on iMinKit

Step 1: Add Application on iMinKit

  1. Navigate to: ☰ iMin Store > ☰ My Apps.

  2. Click the Add App button.

  3. Upload the application APK file, then click the Next Stepbutton.

Step 2: Add Application on KiwiCloud console

  1. Navigate to KiwiCloud console: ☰ App Management > ☰ My App.

  2. Click the Create App button, select 'Add Enterprise Public Apps'

  3. ➊ Read the terms and conditions, ➋ Select the newly added app, then ➌ Click the Add button.

4.2.2 Private Apps

Initiate the adding of private apps on KiwiCloud console

Step 1: Create Application Category

  1. Navigate to: ☰ Application Management > ☰ Application Categories.

  2. Click the Create Application Category button.

  3. ➊ Enter the “Category Name”, ➋ Upload a “Category Icon”, then ➌ Click the Save button.

Step 2: Add Application

  1. Navigate to: ☰ Application Management > ☰ My App.

  2. Click Create App > Publish Enterprise Private Apps button.

  3. Upload the application APK file, then click the Next Stepbutton.

  4. ➊ Select an “Application Category”, ➋ Enter “Supported Devices”, then ➌ Click the Next Step button.

  5. ➊ Configure the application’s permissions (you may leave it unchanged at the default User Controls), then ➋ Click the Submit button.

4.3 Configure Application Release Policy

There are a total of 3 application policies:

  1. App Release Policy

  2. App Update Policy

  3. Kiosk Policy

In this guide, we will use App Update Policy as an example.

Step 1: Configure and Deploy an Application Release Policy

  1. Navigate to: ☰ Application Management > ☰ Application Release Policies.

  2. Click the Create Application Policy > Create KC App Policy button.

  3. ➊ Enter a “Policy Name”, ➋ Enable Compliance Check, ➌ Under Required Apps select the app that was just uploaded, then ➍ Click the Next Step button.

  4. On the Application Configuration 📑 page, ➊ Leave the settings as default, then ➋ Click the Next Step button.

  5. For the deployment scope, ➊ Set Device Release Scope to “Targeted Deployment”, ➋ Select the device group containing the newly enrolled device, then ➌ Click the Submit button.

Step 2: Verify the Policy Deployment Result (Optional)

  1. Console verification: Find the application release policy "VIA" that was just published, click the Detailsbuttonto open the policy details page. Click the Operation Log 📑 tab to check the deployment status.

  1. Device-side verification method 1: Check the device’s home screen to see if the app has been installed.

4.4 Kiosk Policy (Single Application)

Note: IMA Devices only support kiosk policies with single application app mode at the moment. Multi-app kiosk mode is not available for IMA devices.

  1. Navigate to: ☰ Application Management > ☰ Kiosk Policy.

  2. Click the New Kiosk Policy > KMA Kiosk Policy button.

  3. ➊ Enter a “Policy Name”, ➋ Select App Mode, ➌ Under Required Apps select the app that was just uploaded, then ➍ Click the Next Step button.

  4. ➊ Enter an “Exit Kiosk Password”, ➋ Select your preferred configuration, ➌ Click the Next Step button.

  5. Configure your app settings.

    For Device Restrictions, IMA devices do not support this feature.

  6. For the deployment scope, ➊ Set Device Deployment Scope to “Targeted Deployment”, ➋ Select the device group containing the newly enrolled device, then ➌ Click the Submit button.

Once the policy is deployed, the device will be locked to the selected application and can only exit it with the correct password.

Configuration

Secondary Display Ads: Configure ad playback rules and upload content for secondary screen display. Available for KMA and IMA devices.

Permission Settings: Configure cashbox control and third-party app installation permissions for iMin devices only. Centralized permission control per device.

Scanner Settings: Configure scanner parameter rules for devices, supporting model-based or group-based settings to improve scanning accuracy and compatibility

Boot Animation: Set custom startup animations for all iMin devices by uploading a ZIP package. Supports model- and brand-specific configurations.

5. Routine Operational Tasks

5.1 Modify Policy

Step 1: Modify Device Policy Configuration

  1. Navigate to: ☰ Device Management > ☰ Device Policy.

  2. Find the previously created device policy by Policy name or ID, click Action > Edit button.

  3. Modify the device policy settings as needed. Here, for example, changing the Bluetooth Name: ➊ Select “Customize”, ➋ Enter a Bluetooth name (e.g., SG-Store), ➌ Click the Next Step button, then click the Save and Publish button.

Step 2: Verify the Policy Change Result

Please refer to the content in

  1. Recommended Process for Initial Business Configuration

4.1 Configure Device Policy

Step 2: Verify the Policy Deployment Result

5.2 Application Version Upgrade

The version upgrade process differs for each app type —Public and Private.

5.2.1 Public Apps

Step 1: Navigate to iMinKit

  1. Navigate to: ☰ iMin Store > ☰ My Apps.

  2. In the list, find the app and click Updatebutton.

  3. Upload a higher-version APK of the app.

  1. Select your preferred configuration

  2. Review your selections in the preview

  3. Submit

Step 2: Check Application Version Update Result

  1. Device-side verification method 1: On the device, check that the app has been updated (in this example, “Via”). Long-press the app’s icon on the home screen, select App Info from the menu, scroll to the bottom of the screen, and verify the version number is the newly published version.

  2. Other verification methods：

    1. Navigate to: ☰ iMin Store > ☰ My Apps.

    2. In the list, find the app and click the arrowbutton.

    3. Verify the version number is the newly published version.

5.2.2 Private Apps

Step 1: Add a New App Version

  1. Navigate to: ☰ Application Management > ☰ My App.

  2. In the list, find the app, click Action > Add New Version button.

  3. Upload a higher-version APK of the app, then click the Next Step button. `Note: If the uploaded version is lower than the current version, the interface will prompt “App version is too low”.`

  1. Select the “Application Category”, fill in “Supported Devices”, and click the Next Step button.

  2. Click the Submit button to complete publishing the new app version.

  3. To view the version release status, click More > Version List button to see all version information of the app.

Step 2: Check Application Version Update Result

  1. Device-side verification method 1: On t6he device, check that the app has been updated (in this example, “Via”). Long-press the app’s icon on the home screen, select App Info from the menu, scroll to the bottom of the screen, and verify the version number is the newly published version.

  2. Other verification methods：Please refer to the content in

    1. Recommended Process for Initial Business Configuration

4.1 Configure Device Policy

Step 2: Verify the Policy Deployment Result

6. Remote Operations and Troubleshooting

6.1 Remote Operations

Devices under IMA control support the following remote operations:

Action

Description

Associate Device Policy

Bind the selected devices to a device policy. You can choose to immediately push the policy; otherwise, only the binding is established, and the policy will be distributed during the next update.

Associate Application Policy

Assign and associate an application policy to one or more devices. Supports immediate push or deferred push after association.

Associate File Distribution Policy

Assign and distribute file policies to one or more devices. Multiple policies can be selected, and files are distributed as configured without duplication.

Retrieve File

Enable Lost Mode

Place the device into “Lost Mode.” The device will be locked and display a warning message, restricting user operations—suitable for lost or stolen devices.

Device Location

Obtain the device’s most recent location (requires online status and location permission) for recovery or troubleshooting.

Lock Device

Remotely lock the device screen to prevent unauthorized use; supports custom lock screen messages.

Unlock Device

Clear the current lock state (including those triggered by policies or Lost Mode) to restore availability.

Remote Reboot

Send a restart command to one or more devices, suitable for scenarios like remote diagnosis, configuration updates, or version deployment.

Remote Shutdown

Revoke Configuration

Unbind the device from current policies and reset platform-issued settings for redeployment; device record is retained.

Restore Default Policy

Reset the device to the default policy stack, clearing temporary/abnormal configurations to restore stability.

Delete Device

Remove devices from the platform’s device list and unbind them from management. This will not uninstall apps or erase data. The operation is irreversible, so execute with caution.

Clear App Data

Clear local app data (cache, configs, login info, etc.) on the target device without uninstalling apps. Useful for account reset or recovery but may impact usage.

Step 1: Perform a Remote Operation on an Online Device (e.g., Lock Device/Unlock Device)

  1. Navigate to: ☰ Device Management > ☰ Device List.

  2. Find the target device by Device name or Serial Number, and click More > Lock Device button.

  3. Enter a lock password for the device, and click the Submit button.

  4. The interface will display the operation result.

Step 2: Verify the Remote Operation Effect

  1. On the device, the screen will be locked and an “Enter your password” interface will appear.

Step 3: Unlock Device

  1. Click More > Unlock Device button.

  2. Enter a reason for the operation, and click the Confirm button to unlock the device.

  3. The interface will display the operation result.

Step 4: Verify the Remote Operation Effect

  1. On the device, the screen lock will be removed and normal operation of the device can resume.

6.2 Remote Assistance

6.2.1 Existing Remote Assistance App

  1. Navigate to: ☰ Device Management > ☰ Device List.

  2. Find the target device by Device name or Serial Number, and click More > Remote Assistance button.

  3. If the device is online and Unattended Access is enabled, the system will automatically connect to the device and enter the remote assistance page.

  4. At this point, you can directly use your mouse to perform click and click-and-drag actions on the device screen.

  5. If the device is offline or Unattended Access is not enabled, it will prompt “Request failed, the device has not authorized cloud access.”

  6. To enable Unattended Access on the device side: open the Remote Assistance app on the device.

  7. Tap the Enable Unattended button to turn it on.

6.2.2 New version of Remote Assistance + AnyDesk

6.2.2.1 Feature Overview

IMA devices migrated to KiwiCloud come pre-installed with the new Remote Assistance app and AnyDesk by default. Compared with the old solution of iMinkit, the new version adds the ability to visualize remote assistance records on the device, allowing end users to check whether they have initiated a remote assistance request on the device. Remote control is done by the KiwiCloud backend in collaboration with the AnyDesk desktop client, and supports two types of entry: cross-authorization and unattended.

6.2.2.2 Terminologies

  • Remote Assistance App: Device-side portal for "initiating requests/viewing request records/receiving connections".

  • KiwiCloud backend: A desktop/browser platform for remotely initiating, viewing request logs, and injecting commercial licenses.

  • AnyDesk (desktop version): A control tool on your local PC for actual remote connection and operation.

  • Unattended password (KMA device): A fixed password set for KMA devices in KiwiCloud device policies for contactless direct connections.

6.2.2.3 Preconditions and Preparation

6.2.2.3.1 On the Device

Migrated to IMA devices with the new remote assistance app and AnyDesk (Android) pre-installed.

The device can be connected to the Internet normally (stable Wi-Fi/Ethernet is recommended).

6.2.2.3.2 Control Terminal (PC)

AnyDesk desktop version (Windows/macOS/Linux is available) installed.

Have account access to the KiwiCloud backend (device management and remote assistance permissions).

6.2.2.3.3 (Optional) Unmanned configuration

If it is a KMA device, the unmanned password has been configured in the device policy and successfully delivered.

6.2.2.4 Operation Process

6.2.2.4.1 Method 1: Initiate a request from the device

Step 1: Initiate a request

  1. Open the Remote Assistance app on the device

  2. Click to initiate a request.

  3. A prompt will pop up, check the box and select Submit.

Step 2: Initiate a connection

  1. ➊ Navigate to: ☰ Tools > ☰ Remote Assistance.

  2. ➋ Click "Remote Conncetion" to initiate the pairing process. A pop up will appear providing guidance.

  3. Once the preparation is complete, click "Initiate Remote": the system will automatically call the local AnyDesk desktop version and connect directly to the target device.

Step 3: Accept the connection

Unattended: A receive/reject dialog box pops up on the device, and the user needs to click Receive on the device before connecting.

6.2.2.4.2 Method 2: Initiate directly from the KiwiCloud backend

Step 1: Select the device and initiate

  1. ➊ Navigate to: ☰ Device Management > ☰ Device List.

  2. Find the device.

  3. ➋ Click Action, ➌ Click Remote Assistance button.

Steps 2 & 3: Consistent with steps 2 and 3 in step 6.2.2.4.1 Method 1:

Background pop-up window to guide License and AnyDesk client preparation;

Click Initiate Remote.

Unmanned Password Configured (KMA Device): Enter the unmanned password before connecting to enter the remote session directly.

6.2.2.5 View and manage request records

On the device:

  1. Navigate to the remote assistance app.

  2. Click 'View Request History'

Here, you will be able to see the status of the most recently initiated remote assistance requests (Submitted/Accepted/Connected/Closed etc.).

On KiwiCloud console: Tools → Remote assistance, which can be queried and processed according to device, time, and status. This section appears only after a device has submitted a remote assistance request.

6.2.2.6 KiwiCloud vs iMinKit

Dimension

Existing Remote Assistance

New version of Remote Assistance + AnyDesk

Connection Engine

Remote assistance app

New version of Remote Assistance App+AnyDesk

Device-side visibility

No request logs

Devices can view the Request History

Unmanned access

Can only be enabled on the device

Supports configuring a KMA unmanned password in control-side device policies

License management

Free with limited concurrent usage

Backend-guided AnyDesk license injection — licenses can be purchased as needed

7. Viewing and Exporting Reports

7.1 Report Schedule

The report schedule feature allows device, application, and remote assistance report data to be compiled into document format and sent to specified email addresses on a schedule.

  1. To add a new report schedule, click the Create Scheduled Report button at the top right.

  2. ➊ Enter a Report name, ➋ Select the reports to send, then click the Next Step button at the bottom right.​

  3. ➊ Select the details for the report schedule (for example, report format, delivery options, recipient email, and email subject), then ➋ Once all options are set, click Submit.

  4. In the Report Schedule list, click the Details button to view the schedule details. Click the More button, where you can ➊ Select Disable to stop sending report emails, or ➋ Select Run Now to immediately send the report email.

7.2 Device Reports

The Device Reports module provides administrators with comprehensive monitoring and analysis of the operational status of enterprise devices. Through this module, administrators can view devices’ real-time status, online duration, battery level, storage usage, and other information, and generate reports for data analysis and sharing. The module supports multi-dimensional filtering to help administrators quickly obtain the required data.

7.3 Application Reports

The Application Reports module is used to generate and view information on the installation and usage of applications on enterprise devices, as well as summary information of blacklisted applications. Administrators can use this module to understand details such as each application’s installation count, version distribution, and device usage, in order to optimize application deployment and management strategies. Application reports support multi-dimensional data filtering for convenient analysis.

7.4 Remote Assistance Reports

The Remote Assistance Reports module is used to generate and view records of enterprise remote assistance sessions. Administrators can use this module to see details such as the number of remote sessions, completion rate, unattended status, etc. The reports support multi-dimensional data filtering to facilitate data analysis.

Note: Application Reports are only available in KiwiCloud Enhanced Version.

8. Unlock More with IMA Upgrades

Get the following capabilities by upgrading your IMA devices!

AI Service
An always-on assistant that handles routine questions and routes edge cases to your team—helping improve first-response time and consistency.

Geofencing / Tracking / Geofence Log
Live device visibility with zone-based alerts. Historical geofence logs add traceability for audits and incident reviews.

App Report / Report Subscription
Scheduled reports on installs, versions, and compliance delivered to email — so stakeholders stay informed without logging in.

If you’d like to upgrade, please contact your enterprise administrator or the KiwiCloud Support team.

Related Articles
Selecting Management Method and Device Type
KMA Quick Start
Video walkthroughs
GMA Quick Start
Registration Management
Did this answer your question?