1. Feature & Application Objectives
Module Purpose:
Notification provides a single place to review the result notifications of management operations on the platform. When a policy push, remote operation, app deployment, or device enrollment completes, the system generates a notification entry. If the operation contains failures, the sidebar icon shows a red dot to alert administrators, who can then filter notifications by operation type, status, and time range, view details, and mark them as read or ignored.
Notification shares the same data as the operation results in each module, so administrators can trace all recent operations in one place instead of checking each module individually.
Notification Rules:
Notifications are generated per operation and cover four categories: Policy (Device Policy / App Release Policy / Kiosk Policy / App Update Policy / File Distribution Policy), Remote Command, App Deployment, and Enrollment;
Operations with failures trigger the red dot on the sidebar icon; fully successful operations are recorded only and do not trigger the red dot;
Notifications older than 30 days are archived automatically and hidden from the default list; switch the time range to “All” to view them;
Critical failures such as policy push failures, single-device remote operation failures, and device enrollment failures are also emailed to administrators; failures in batch remote operations and app deployment failure-rate alerts are not emailed.
Primary Operations:
View and filter notifications: browse the list by operation type, status, and time range;
View details: open the full content of a notification and go to the related operation.
Secondary Operations:
Ignore: de-emphasize notifications that are acknowledged but not to be handled now;
Mark All Read: mark every unread notification under the current filter as read in one click.
Typical Use Cases:
Some devices fail to receive a policy push; the administrator notices the red dot and goes straight to the failure details;
After a batch remote operation, review which devices failed without checking them one by one;
Trace devices that failed to enroll in the last 30 days to troubleshoot zero-touch or QR code enrollment settings;
Periodically clear handled notifications so that pending items stay visible.
2. Primary Operations
2.1 View and Filter Notifications
Description
Notification lists all notification records of the current enterprise. Each entry shows the notification content, level, operation type, status, and time. Three filters at the top of the page (operation type, status, and time range) narrow the list; the default view shows the last 30 days.
Steps
Open Notification
In the left navigation, click System Management ➊ > Notification ➋ to open the notification list.
Set filters
➊ Operation Type: Policy / Remote Command / App Deployment / Enrollment;
➋ Status: Unread / Read / Ignored;
➌ Time range: Today / Last 7 Days / Last 30 Days / All (including archived notifications).
Run the query
Click Search ➍ to refresh the list, or Reset to restore the default filters.
The total and unread counts for the current filter are shown above the list.
Notes
Unread notifications are marked with a green dot before the content; ignored notifications stay in the list and can be viewed separately with “Status = Ignored”;
Selecting the “All” time range includes archived notifications older than 30 days, so the query may take slightly longer;
The list is sorted by time in descending order, and the page size can be changed.
2.2 View Notification Details
Description
Details shows the complete information of a single notification, including content, level, operation type, status, and time. Viewing the details marks the notification as read automatically.
Steps
Open the details
In the Action column ➋ of the list, click Details on the right of the target notification.
Review and handle
Check the content and the related object (such as the policy name or device serial number), then go to the corresponding module to resolve the failure.
Notes
Clicking Details changes the status from “Unread” to “Read”;
If the related object has been deleted (for example, the policy no longer exists), navigation to its details page may not be available.
3. Secondary Operations
3.1 Ignore
Description
Ignore de-emphasizes a failure notification that has been acknowledged but will not be handled for now, keeping the list tidy. Ignored notifications are not deleted and can be reviewed at any time through the status filter.
Steps
Ignore a notification
In the Action column of the list, click Ignore ➊ on the right of the target notification. Its status changes to “Ignored”.
Notes
Only failure notifications have an Ignore button; fully successful notifications do not need to be ignored;
Ignored notifications no longer show the Ignore button, but Details remains available.
3.2 Mark All as Read
Description
Mark All Read marks every unread notification under the current filter as read in one click, which is useful after a batch of issues has been handled.
Steps
Notes
Mark All Read applies only to unread notifications under the current operation type and time range filters, and does not affect ignored notifications;
Marking as read does not mean the issue is resolved; the failure still needs to be handled in the corresponding module.
4. Field Descriptions
Field | Description |
Content | Title and summary, e.g. “Remote operation failed: {device serial number}”; the summary carries the related object and the failure reason code. |
Severity | Severity of the notification. Operations with failures show “Error”; fully successful operations show success. |
Operation Type | Category of the operation that produced the notification: Policy / Remote Command / App Deployment / Enrollment. |
Status | Unread / Read / Ignored. Becomes Read after viewing details or “Mark All Read”; becomes Ignored after clicking “Ignore”. |
Time | When the notification was generated. |
Action | Details / Ignore. |
Trigger Rules
Policy push (Device Policy / App Release Policy / Kiosk Policy / App Update Policy / File Distribution Policy): a failure notification is generated and an email is sent when any device fails to receive the policy; a fully successful push is recorded only;
Remote operation: a failure on a single device generates a failure notification and an email; a batch operation with failed devices generates a failure notification without email;
App deployment: a failure notification is generated when the app installation or update failure rate exceeds the alert threshold; no email is sent;
Enrollment: a failure notification and an email are generated when a QR code enrollment fails on a device, or when a KiwiCloud Zero-touch or Google Zero-touch configuration has devices that failed to enroll.






