KiwiCloud supports a variety of remote actions for registered KMA-type devices, categorized into batch actions and single-device actions. Remote actions are a key capability of the platform, enabling real-time device management, policy delivery, and security control.
1. Overview of Remote Action Capabilities
Action Name | Batch Action | Single Device Action | Description |
Add to Group | ✅ |
| Add selected devices to one or more device groups. If the group is already associated with policies, users can choose whether to push them immediately. If not selected, only the association will be created without immediate delivery. |
Associate Device Policy | ✅ |
| Associate the selected devices to a device policy. Users can choose whether to push the policy immediately or only establish the binding relationship. The policy will be pushed when needed. |
Associate Application Policy | ✅ |
| Associate one or more devices with an application policy. Supports immediate push or deferred binding for future deployment. |
Associate File Distribution Policy | ✅ |
| Manually select and push file distribution policies to one or more devices. Multiple policies can be selected at once, and duplicate files across policies will be deduplicated automatically before delivery. |
Remote Reboot | ✅ | ✅ | Send reboot commands to one or more devices. Applicable to remote diagnostics or rebooting after configuration changes. |
Remote Shutdown | ✅ | ✅ | Send shutdown commands to one or more devices. Applicable to power-saving, device maintenance, or fault recovery scenarios. |
Retrieve Files |
| ✅ | Select files from the public directory of the device and transfer them to the platform for download. Supports multiple files at once; limited by total file size, not by number of files. |
Enable Lost Mode |
| ✅ | Enable lost mode for the device. The device will be locked, continuously ring, and report its location. Applicable in scenarios such as lost or unauthorized device use. |
Disable Lost Mode |
| ✅ | Disable the device’s lost mode, stop the ringing, and unlock the device. Applicable when the device has been recovered. |
Lock Device |
| ✅ | Remotely lock the target device, set a password and a custom message to prevent unauthorized use. Once locked, the “Unlock Device” option will become available. |
Unlock Device |
| ✅ | Clear the lock state and the on-screen password prompt to restore the device to normal use. This option is only available when the device is already locked. |
Revoke Configuration |
| ✅ | Remove the device from its current configuration. Optionally wipe device data and set the device status to “unenrolled”, “Retired”, or “Under Repair”, applicable to recovery, redeployment, or maintenance scenarios. |
2. Batch Device Actions
2.1 Add to Group
Description
This action is used to add one or more devices to one or more designated device groups. Each group can be bound to multiple policies (such as device policies, application policies, etc.), and users can flexibly choose whether to apply those policies immediately.
KiwiCloud allows a single device to belong to multiple groups. The “Add to Group” operation is one of the core processes for managing device group strategies.
Steps
Select Target Devices In the Device List, select the desired devices and click “Add to Group” to open the operation panel.
View Selected Device List The top of the page displays all selected devices, including basic information such as name, model, manufacturer, and serial number, for user confirmation.
Select Target Groups
The middle section lists all available device groups.
The right side of each group shows:
Device Count: Number of devices currently in this group;
Policy Count: Number of policies associated with this group;
Apply Group Policy (single-choice): If selected, the group's policies will be applied to the selected devices.
Multiple groups can be selected, but only one group can have “Apply Group Policy” enabled at a time.
View Policies to Be Applied
If “Apply Group Policy” is selected, the page will show the list of currently active policies for that group at the bottom.
Users can check specific policies to apply or leave them all unchecked (this means only the association is created, without policy delivery).
Submit Action
Click “Submit” to complete the action.
The selected devices will be added to the chosen groups, and the selected policies will be pushed depending on your selections.
Notes
If “Apply Group Policy” is selected, the system will automatically list the associated and currently active policies of the group.
All policies are selected by default, meaning they will be pushed immediately to the devices.
Users can uncheck any policy to indicate that only the association is established without triggering delivery.
Group policies are pushed only when the device is online; offline devices will receive them once they come online.
To adjust policies later, go to the “Device Detail > Policies” tab for management.
You can view device group associations in the “Device Detail > Groups” tab.
2.2 Associate Device Policy
Description
This action is used to manually bind a device policy to one or more devices. It applies to scenarios where control is not performed via groups, and where policies need to be directly pushed or pre-bound to specific devices.
Device policies cover essential configurations such as system settings, security permissions, and feature restrictions. They are a core tool for centralized device management.
⚠️ Only one device policy can be bound per operation.
💡 KiwiCloud uses a configuration stacking mechanism for device policies: if multiple policies are applied in sequence, the later one will overwrite any overlapping configuration items from the previous policy.
Steps
Select Devices
In the Device List, check the target devices;
Click the “Associate Device Policy” button to enter the policy selection page.
Confirm Device Type
The top of the page displays the basic information of all selected devices.
Select Device Policy
The middle section displays all available device policies (filtered by device type);
Only one policy can be selected per operation;
Supports page-by-page browsing and viewing of policy versions.
Confirmation Prompt Before Submission
After clicking “Submit”, the system will display a confirmation pop-up: “Do you want to push the policy now?”
Click “Yes”: the policy will be immediately pushed to the devices;
Click “No”: only the binding relationship will be established; the policy will not take effect immediately.
Complete the Action
After completion, the bound policy and its effective status can be viewed under Device Detail > Policy tab.
Notes
Each operation supports binding only one policy;
Each device can only have one active policy at a time. A newly bound policy will overwrite the existing one;
If “No” is selected, the policy binding will be created, but the policy must be manually pushed later;
If “Yes” is selected, the policy will be pushed to the device immediately;
You can verify policy delivery and execution status via Operation Logs and System Logs.
2.3 Associate Application Policy
Description
This action is used to manually bind an Application Policy to the selected devices. It supports batch operations and is suitable for flexible policy scheduling or temporary adjustment scenarios. After the operation, the system will prompt whether to immediately push the policy.
⚠️ Only one application policy can be bound per operation.
💡 KiwiCloud uses a configuration stacking mechanism for application policies: later-pushed policies will override any overlapping configuration items from earlier ones.
Steps
Select Target Devices In the Device List, check one or more devices and click “Associate Application Policy” to enter the operation interface.
View Device Information The top of the page lists basic information of the selected devices (device name, model, manufacturer, serial number) for confirmation.
Select Target Policy The bottom of the page displays all available application policies, including policy name, policy ID, and the latest version number.
Only one policy can be selected for binding;
You may browse all policies using pagination.
Submit and Confirm
After clicking “Submit”, the system will prompt: “Do you want to push the policy now?”
Selecting “Yes” will push the policy immediately to the devices;
Selecting “No” will only create the binding relationship without immediate delivery.
Notes
Only one policy can be bound per operation; multiple selection is not supported;
Policy delivery requires the device to be online; offline devices will receive it once they come online;
If a device already has an existing policy of the same type, overlapping configuration items will be overwritten by the new one;
You can check current bound and active policies under Device Detail > Policies;
It is recommended to combine Device Policies and File Distribution Policies for comprehensive policy control.
2.4 Associate File Distribution Policy
Description
This action is used to apply one or more file distribution policies to selected devices. Through this feature, administrators can batch distribute configuration files, resource files, upgrade packages, etc., to endpoint devices.
⚠️ If multiple policies contain duplicate file content, the platform will automatically perform deduplication to ensure each file is distributed only once, avoiding redundant resources.
Steps
Select Target Devices In the Device List, select the required devices and click “Associate File Distribution Policy” to open the operation page.
Confirm Selected Devices The top of the page lists basic information of the selected devices (device name, model, manufacturer, serial number, etc.) for user confirmation.
Select Available Policies
The bottom section displays all available file distribution policies;
Each policy includes: policy name, policy ID, and latest version number;
Users may select one or more policies. The platform will distribute the content to devices once they come online.
Submit and Apply Click the “Submit” button in the bottom right corner of the page. The system will establish the policy binding and immediately initiate delivery.
Notes
A single device can be associated with multiple file distribution policies simultaneously;
Files within the policies will be deduplicated before distribution to avoid redundant resources;
Offline devices will automatically receive tasks upon coming online;
If policy execution fails, the failure reason can be viewed in the Operation Logs or System Logs.
2.5 Remote Reboot
Description
The “Remote Reboot” action allows administrators to remotely reboot devices from the platform without needing on-site personnel. It is commonly used to apply new configurations or to quickly recover devices showing abnormal behavior.
⚠️ Remote reboot requires the device to be online and the KC App to be running properly. The command will be issued immediately and cannot be revoked.
Steps
Select Target Devices In the Device List, select one or more devices and click “Remote Reboot”.
Confirm Execution Prompt A confirmation dialog will appear: “Are you sure you want to reboot these X devices?”
Click “Confirm” to issue the reboot command;
Click “Cancel” to abort the operation.
View Execution Status After the operation is submitted, go to Operation Logs to check the result for each device (success/failure).
Notes
Only online devices can receive and execute the remote reboot command immediately;
Offline devices will not cache the command and will not execute it upon coming online;
Devices will briefly go offline during reboot—avoid performing this action during business peak hours;
It is recommended to ensure all configuration changes are saved before rebooting to avoid data loss.
2.6 Remote Shutdown
Description
The Remote Shutdown action allows platform administrators to remotely power off devices. It is suitable for scenarios such as device malfunction, power saving after business hours, or preparation before remote maintenance. Once executed, the device will shut down and must be manually powered on onsite.
⚠️ Use with caution. Once a device is shut down, it cannot be powered on again remotely.
Steps
Select Target Devices In the Device List, check one or more devices and click “Remote Shutdown”.
Confirm Execution Prompt A confirmation dialog will appear: “Are you sure you want to shut down these X devices?”
Click “Confirm” to immediately issue the shutdown command;
Click “Cancel” to cancel the operation.
View Execution Status You can go to Operation Logs to check whether each device successfully executed the remote shutdown command.
Notes
Only online devices will receive and execute the shutdown command; offline devices will not execute it;
Once shut down, the device must be manually powered on onsite;
It is recommended to notify relevant personnel in advance to avoid business interruptions.
3. Single Device Actions
3.1 Retrieve Files
Description
Retrieve Files allows you to remotely extract specific files from a device’s public directory (such as /Download) when the device is online, and upload them to the platform for download. This feature is useful for troubleshooting, log collection, content export, and similar scenarios.
The system allows users to freely select the desired files, with a total data transfer limit of 200MB per operation. There is no limit on the number of files.
Note: Only public directories on the device are accessible. Restricted or private system directories cannot be accessed.
Steps
Select Device In the Device List, click the target device to enter the device detail page, then click “Retrieve Files”.
View File List The system displays all accessible files currently available in the device’s public directory, with icon previews and file sizes.
Select Desired Files
Select multiple files as needed. The lower-left corner shows the total size (in MB) of the selected files in real time.
If the size exceeds 200MB, an error message will be shown and the submit button will be disabled;
If within the limit, you may proceed.
Submit File Request Click “Submit”. The system will request the device to upload the selected files to the KC cloud.
View and Download
Once the upload is successful, the system will automatically redirect to the Download List page. You can then click the download button beside each file to save it locally.
Notes
Currently, only public directories on the device (such as
/Download) are accessible;The total file size in a single operation must not exceed 200MB, otherwise submission will be blocked;
There is no limit on the number of files selected;
This operation only works when the device is online; it will fail if the device is offline;
Retrieved files are temporarily stored on the platform—please download them promptly;
Any file type is supported—there are no format restrictions.
3.2 Enable Lost Mode
Description
Enable Lost Mode is a critical security feature provided by KiwiCloud for fully managed Android devices owned by the company. In cases where a device is lost, stolen, or used abnormally, administrators can remotely lock the device, trigger a warning ringtone, and locate the device.
Once Lost Mode is enabled, the corresponding Disable Lost Mode action will automatically become available. The administrator or device user can exit the locked state according to defined rules.
Effects After Enabling
The device immediately enters a locked state, preventing normal user operations;
A loud ringtone plays continuously for 5 minutes, with maximum volume enforced;
The device automatically reports its current location;
The “Disable Lost Mode” button appears on the device’s detail page;
The device status is set to Lost;
The device can be unlocked by entering the preset password or via backend operation.
Steps
Open the Action Interface On the single device detail page, click “Enable Lost Mode”.
Fill in Required Information
Set a unlock password;
Enter the reason for this action for audit logging;
Submit and Confirm After submission, the platform sends the command to the device, which will then enter Lost Mode.
Activate “Disable Lost Mode” Function Once enabled, the device’s detail page on the platform will display a “Disable Lost Mode” button.
Notes
Once enabled, the platform and device will both store the unlock password—please do not lose it;
This operation is irreversible; Lost Mode can only be exited via password or backend action;
The ringtone does not repeat automatically. To ring again, Lost Mode must be re-enabled;
The “Disable Lost Mode” option is only visible after enabling. It does not appear under normal conditions.
3.3 Disable Lost Mode
Description
Disable Lost Mode is the companion command to “Enable Lost Mode”. When a device is in Lost Mode, it is forcibly locked and rings continuously. Administrators can execute “Disable Lost Mode” once the device is recovered or locking is no longer necessary.
This operation clears the device's lock password and stops the ringtone, restoring the device to normal use.
Prerequisite: The device must already be in Lost Mode.
Effects After Execution
Clears the device’s lock password;
Immediately stops the ringtone;
Restores normal usability of the device;
The “Lost” status will be removed on the platform.
Steps
Access the Operation
The “Disable Lost Mode” button will only appear on the device detail page when the device is currently in Lost Mode.
Enter Operation Reason
The system requires a reason for the operation for audit logging;
Examples: Device recovered, cancel due to misoperation, etc.
Submit the Operation
Click “Confirm” to submit the command. The device will then unlock and stop ringing.
Notes
The device must be online for the operation to succeed;
After disabling, Lost Mode must be re-enabled to take effect again;
This action is irreversible and takes effect immediately upon submission;
The operation record will be logged under “Action Logs” for audit tracking.
3.4 Device Location
Description
The Device Location feature helps users quickly retrieve the current geographic location of a device. It also allows checking whether location services are enabled on the device, making it suitable for troubleshooting abnormal positioning or tracking lost devices.
The system displays the most recent location reported by the device, including:
Device location (on map)
Timestamp of the report
Precise coordinates (latitude & longitude)
Location status (enabled/disabled)
Access Paths
Entry Method | Description |
Actions Menu - Device Location | In the device list, click the [Actions] button on the right side of a device, then select “Device Location” to open the popup directly. |
Detail Page - Location Trace Tab | On the device detail page, click the “Location Trace” tab to view the map and location info card. You can also enable Lost Mode and check location history from here. |
Displayed Information
Field | Description |
Device SN | Serial number of the current device being located |
Last Updated | Timestamp of the most recent location report |
Last Location | Geocoded address from GPS or IP (province/city/district + street) |
Coordinates | Precise longitude and latitude |
Location Status | Whether location service is currently enabled on the device |
Quick Actions (Detail Page Only)
Action Button | Description |
Enable Lost Mode | Starts Lost Mode to force device lock, sound alarm for 5 minutes, and continuously report location |
Location History | View historical location trail of the device (if history tracking is enabled) |
Notes
Device must be online and have location permission enabled to return latest location data;
If the reported location hasn’t been updated for a long time, the device may have disabled location, be offline, or lack network access;
Supports both GPS and IP-based positioning—accuracy may vary with network conditions;
Enabling Lost Mode will automatically activate the location function;
The “Device Location” action is only available for individual devices, not batch operations.
3.5 Lock Device
Description
The Lock Device feature allows administrators to remotely lock a specified device by setting an unlock password and a screen message. Locked devices cannot be operated unless the correct password is entered or unlocked remotely from the platform. This function is typically used in urgent control or policy violation scenarios.
Lock and Unlock are paired operations:
The “Unlock Device” menu item appears only when the device is in a locked state;
Once unlocked, the “Unlock” option disappears and reverts to “Lock Device”.
Steps
Access the Lock Device Interface
Click “Lock Device” from the device detail page or the operations list;
Set Lock Parameters
Enter the lock password required to unlock the device;
Provide a screen message, which will be displayed on the locked screen (e.g., "Please contact your administrator");
Confirm and Submit
After submission, the command will be pushed to the device.
Notes
The device must be online for the operation to take effect immediately;
The screen message will be visible to the device user—make sure the content is clear and appropriate;
Locking the device does not affect platform communication or other remote operations;
Lock Mode is not equivalent to Lost Mode; the two features function independently.
Unlock Methods
The user can manually enter the preset password on the device to unlock;
The administrator can remotely unlock the device using the Unlock Device feature.
3.6 Unlock Device
Description
The Unlock Device feature allows administrators to remotely clear a device's locked status, including the lock screen password and message previously set via the "Lock Device" operation. Once completed, the device returns to normal use and the lock screen is no longer displayed.
This option is only available when the device is already in a locked state, and it serves as a paired action to the “Lock Device” command.
Steps
Open the Unlock Device Interface
The “Unlock Device” button appears only after the device has been remotely locked.
Enter Unlock Reason
The system will prompt for a reason, which is recorded for future auditing and tracking.
Confirm Unlock Action
Click “Confirm” to trigger the unlock command.
If the device is online, it will be unlocked immediately. If offline, the command will execute once it comes online.
Notes
This action cannot be undone. Ensure identity and permission verification before proceeding.
Unlocking will clear all lock-related information previously set via “Lock Device”.
It will not affect apps, policies, or any other content on the device.
The unlock action is recorded in the operation logs for audit and traceability.
Unlocking is not the same as exiting Lost Mode—do not confuse the two features.
3.7 Remote Reboot
Same as 2.5 Remote Reboot
3.8 Remote Shutdown
Same as 2.6 Remote Shutdown
3.9 Remote Assistance
To be added
3.10 Revoke Configuration
Description
The Revoke Configuration function is used to release the device from its current managed state. Administrators can choose whether to wipe data and define the device’s subsequent status based on business needs. This operation applies to scenarios such as device retirement, decommissioning, repair, or redeployment.
There are two operation modes:
Mode 1: Wipe Device Data
Operation content:
Perform factory reset on the device, erasing all local data (including SD card);
Optionally remove the device from the platform;
Set the post-operation status of the device to:
Unenrolled: The device remains on the platform and can be re-initialized later;
Retired: The device is marked as permanently out of service.
Mode 2: Do Not Wipe Device Data
Operation content:
No data will be wiped;
Set the device status to Maintenance, meaning the device is still operational but will be reset in configuration;
A default policy will be pushed to the device to ensure minimal control.
Steps
Select Target Device
In the device list, click on a single device and choose “Revoke Configuration”.
Configure Revoke Options
Whether to wipe data: Yes / No
Define device status:
If wiping: Unenrolled / Retired
If not wiping: Maintenance
Enter Operation Reason
An explanation is required for auditing purposes.
Submit and Confirm
Click “Revoke Configuration”, confirm via the pop-up prompt to execute the operation.
Notes
Device must be online to execute the factory reset;
Devices in Retired status cannot be re-registered—use only for permanent deactivation;
All data will be permanently deleted after a factory reset;
Devices in Unenrolled status retain their records and may be re-registered;
Maintenance status is suitable for repairs, diagnostics, or temporary disablement.