A SaaS provider publishes core apps to the platform for specific enterprise customers;

IT administrators at headquarters share standardized business apps with regional branches;

Channel integrators distribute utility or service apps to multiple clients;

Custom developers use KiwiCloud to distribute proprietary APKs for client-specific needs.

This feature is suitable when your organization wants to provide a self-developed app to other customers or subsidiaries.

All published apps will appear in the “My Apps > Add Enterprise Public App” section of the target enterprise.

After publishing, the app enters a “Pending Review” status. It will only become active upon approval.

Target scope includes your own organization, its sub-organizations, and other platform organizations.

“Select Enterprise” displays the current org and its sub-orgs;

“Import/Input Enterprise ID” allows targeting external orgs – make sure the ID is correct;

After publishing, the app enters a “Pending Review” status and must be approved by KiwiCloud admin to go live;

Apps in "Pending Review" status support Approve or Cancel Publish actions;

To update the app, it’s recommended to cancel and republish.

Only apps in Draft / Published / Unpublished status are supported;

Each tab displays information for the currently selected version, which can be switched via the version dropdown at the top;

Permissions are parsed by the system and cannot be edited on this page;

To edit version content, return to the main list and use Edit or Add New Version.

App category (e.g., Tool, Security)

Package name

Version code

Compatibility scope

Supported devices

description

Permission items (e.g., Storage, Camera, Location)

Permission control policies (Allow / Deny / User Control)

Scope: All / Part;

List of target organizations (Name, ID, Location);

Operation type (e.g., Publish Public App, Edit App Info)

Operator, result, and timestamp

Supports pagination and export

System responses (success/failure)

Supports time-based filtering

Only apps in Draft status can be submitted;

After submission, a Cancel Publishing button becomes available;

If the submission is rejected, the app will revert to Draft status and must be modified before re-submission;

Once submitted, the app enters the publishing workflow and cannot be edited—ensure all configurations are correct before submission.

Submitted apps cannot be edited; to make changes, cancel the submission first;

Before approval, the app will not be visible to other organizations or appear in the "Enterprise Public Apps" list;

All submission and approval actions are logged for auditing purposes;

There is no confirmation popup—review version and configuration details carefully before submitting.

All fields are editable. Changes to description and category do not require approval and take effect immediately upon saving. Modifications involving the icon, APK file, permissions, or release scope require re-submission for approval;

Edits will not impact devices that already have the current version installed;

If you need to publish a brand-new version, it is recommended to use Version Management > Add Version;

Apps that are currently under review cannot be edited again until the review is completed or canceled;

All edit actions are recorded in the operation logs for audit purposes.

You can start the version addition process from two entry points:

The APK package name must be identical to the original version;

The version number must be higher than the currently highest version;

Once added, the app enters Pending Review status. It becomes effective after approval;

Older versions remain unaffected and can coexist with the new version;

If any enterprise is using "Latest Version" in their app publish or update strategy, the approved new version will be automatically pushed to their target devices for upgrade;

To perform a staged rollout, use the Partial Enterprises option in the release scope to control version visibility.

The list displays data at the version level—each version has an independent status;

Draft versions can be edited and submitted; Published versions can only be unpublished, not edited;

If an enterprise uses the "Latest Version" strategy, publishing a new version will automatically trigger an update;

If multiple versions are in the "Published" state, only the latest version will be used as the default recommendation;

Unpublishing a version does not affect its usage on existing devices—it only limits future distribution and policy targeting.

Only versions in Published status support the unpublish operation;

This operation is irreversible. To republish the version, you must manually re-execute the publish operation;

Once unpublished, the following impacts will occur:

Unpublishing affects platform-level distribution and visibility only. It will not uninstall the app from any device that already has it installed.

Only versions with the status Unpublished support the Republish Version action;

After initiating the action, a confirmation popup will appear. The operation takes effect once you click [Confirm];

Once republished, the version becomes visible again in "Add Enterprise Public App" under My Apps;

This operation does not affect other versions or override the current default distribution version;

If you're promoting a newer version, it's recommended to use "Add Version" instead of republishing an older one.

Only apps in the Pending Review status support this action;

Once canceled, the current publication process is terminated and the app is removed from the "App Publishing Queue";

A confirmation popup will appear. Once confirmed, the operation is irreversible;

The app status changes to Draft, enabling you to modify and resubmit;

Other published versions of the app remain unaffected;

To completely remove an app, use the Unpublish Version or Delete option (if available);

Canceling publication does not affect any devices that have already deployed the app.

Only apps in the Published status can be unpublished;

A confirmation popup will explain the impact and irreversibility of this action;

Once confirmed, the following will occur:

The app will be removed from the “Add Enterprise Public App” page for all enterprises;

Other enterprises cannot re-upload the same app (package name conflict remains in effect);

Enterprises that previously added the app will see its status marked as Unpublished in “My Apps”;

Existing installations remain usable without interruption;

If the app is included in any App Distribution, App Update, or Kiosk strategy that has not yet been executed:

Only apps in the Unpublished status support the Republish operation;

A confirmation popup will appear before execution; users must confirm manually;

Once confirmed, the action is immediate and irreversible;

After republishing, the following impacts will occur:

The app will reappear in the App Library > Add Enterprise Public App interface for enterprise users;

Enterprises that had previously added the app will see its status change back to Published in “My Apps”;

If the app is included in the following strategies and they have not yet been executed, it will be installed during execution:

Once republished, the app will rejoin the strategy execution workflow.

Only apps in Draft or Unpublished status can be deleted;

This action is irreversible once confirmed;

Deleting an app will permanently remove the record but will not affect usage on already deployed devices;

After deletion, you can re-upload an app with the same package name.

The app will no longer appear in the App Library > Add Enterprise Public App interface;

For enterprises that previously added the app, its status will remain as Unpublished in “My Apps”;

If the app is included in any of the following strategies but not yet executed, it will be skipped during execution:

If the app is re-published, it will not rejoin any previously configured strategies.