Part 1 of 3

Part 2

Part 3

 

This step-by-step guide shows how to upload internal apps (apks you’ve developed) to the Android Managed Play Store for your organization via Workspace ONE. Subsequent sections also show how to add other versions for Alpha/ Beta testing in the Google Play console, then manage assignment of those versions to specific devices/ users in Workspace ONE.

 

Pre-requisites:

  1. Workspace ONE environment already registered to Android EMM

1-1.png

  2. Apk file with an application ID that has not been published in the Android public play store.

 

A. Publish a New Application

1. Login to the Workspace ONE UEM console.

2. Go to Apps & Books\ Applications\ Native\ Public\ Click “Add Application”.

3. Select Platform: Android. Name can be kept blank. Click “Next”.

2-3.png

4. Select the private apps icon on the left.

2-4.png

5. Click the “+” button to add a new app.

2-5.png

6. Make sure to add a Name, then select “Upload APK”.

2-6.png

The “Create” button will be enabled if the app can be uploaded.

2-6-2.png

7. You will see the app in the Private apps section, and a notification that publishing in your store may take up to 10 minutes.

2-7.png

8. Close this screen. The app you just uploaded will be the app list under Public apps.

2-8.png

(Optional) To edit the logo shown in the console, click on the pencil icon beside the app.  Note that this only updates the icon in UEM, not in the Play store.

2-8-2.png

2-8-3.png

9. Save and assign the app.

2-9.png

10. Click Add Assignment

2-10.png

11. Pick the organization group/ smart group you would like to assign the app to. Click add.

2-11.png

12. Update Assignment pop-up will appear. Click “Save and Publish” to confirm. Then “Publish” at the Preview Assigned Devices page.

2-12.png

2-12-2.png

13. You will return to the app list screen. If the deployment is set to “Automatic”, app will get installed automatically on the device and show in both the Workspace ONE Hub/ Catalog and the  Google Play Store.

2-13.png

2-13-3.png2-13-2.png

 

(continues to Part 2)