Skip to main content

App Push Restriction

How to add, search, edit, and delete App Push Restriction rules, with field descriptions.

1. Feature & Application Objectives

Module Purpose:

The App Push Restriction module maintains, per device group, a list of apps that should not be delivered. When a policy is pushed, the system matches the app package names configured in the rule; a matched app is skipped, and neither its installation nor its configuration takes effect on the device. Administrators can create restriction rules for all devices or for specific groups, excluding apps that do not apply to certain groups without changing the policy itself.

The feature corresponds to the group blacklist and app store blacklist in iMinKit, so the same management approach can be kept after migrating to KiwiCloud.

App Deployment Restriction Rule Notes:

  • The restriction applies only to policy delivery on the platform; it is not an installation block on the device and does not affect apps already installed;

  • Restricted apps can only be selected from public apps; package names cannot be typed in manually;

  • The scope can be “All” or “Group”; with “Group”, whether a device is affected is decided by the group it belongs to once the rule is saved;

  • During policy push, apps are matched by package name. A matched app is skipped, and its installation and configuration do not take effect on the device.

Primary Operations:

  • Add Rule: configure the list of apps to skip for all devices or for a specific group.

Secondary Operations:

  • Search: find existing rules by keyword;

  • Edit / Delete: adjust or remove existing rules.

Typical Use Cases:

  • One App Release Policy covers several store groups, but a few groups should not receive certain apps;

  • Customers migrated from iMinKit need to keep their existing group blacklist configuration;

  • A pilot group should not receive a new app until it has been validated.

2. Primary Operations

2.1 Add Rule

Description

Add Rule creates a new app deployment restriction rule by specifying the scope (All or Group) and the public apps to skip. Once saved, the rule takes part in matching for all subsequent policy pushes.

Steps

  1. Open the add window

    al-list
    • In the left navigation, click Configuration > App Push Restriction ➊, then click Add Rule ➋ at the top right of the list to open the “Create App Deployment Restriction” window.

  2. Fill in the rule information

    al-add-top
    • ➊ Rule Name (required): a name used to identify the rule in the list;

    • ➋ Restriction Scope: select “All” or “Group”;

    • ➌ Select Group (required when the scope is “Group”): choose the device group the rule applies to.

  3. Select restricted apps

    al-add-apps
    • In the “Restricted Apps” area, search public apps by App Name or Category ➊;

    • Tick ➌ the apps to skip; switch to the “Selected” tab ➋ to review the chosen apps.

  4. Save the rule

    • Click OK ➍. The rule appears in the list and takes effect immediately.

Notes

  • Restricted apps can only be selected from public apps; package names cannot be typed in manually;

  • With the “Group” scope, matching is based on the group a device belongs to; a device removed from the group is no longer affected by the rule;

  • The rule affects only subsequent policy pushes; it does not uninstall or block apps already installed on the device.

3. Secondary Operations

3.1 Search Rules

Description

A keyword search above the list helps locate a rule quickly when many rules exist.

Steps

  1. Enter a keyword

    al-search
    • Type a keyword in the search box ➊ and click Search ➋; click Reset ➌ to clear the condition.

3.2 Edit and Delete

Description

In the Action column, click Edit to adjust a rule or Delete to remove it. An edited list applies from the next push; after deletion, the restricted apps are delivered normally again.

Steps

  1. Edit

    al-actions
    • Click Edit ➊ on the right of the rule, adjust it, and click OK.

  2. Delete

    • Click Delete ➋ on the right of the rule and confirm.

Notes

  • Deleting a rule does not re-deliver apps skipped earlier; push the policy again if needed;

  • Last Modified By and Update Time record the latest change.

4. Field Descriptions

Field

Description

Rule Name

Name of the rule; required.

Restriction Scope

All / Group. With “Group”, matching is based on the device’s group.

Device Group

The device group the rule applies to; required when the scope is “Group”.

Restricted Apps

Public apps to skip during delivery, matched by package name.

Last Modified By / Update Time

The account and time of the latest change to the rule.


​

Did this answer your question?