After successfully configuring and deploying AirWatch Launcher to your fleet of devices, the app is now ready to be used in your organization.

Depending on the device, OS being used, and the version of Launcher, the profile may require the user to grant app permissions and set AirWatch as the default launcher. Granting app permissions allows AirWatch to push Launcher settings to control the device, and setting AirWatch Launcher as the default overrides the native launcher on the device.

Once users have prepared their devices, they can further customize the Launcher layout by adding folders and widgets, and other elements. Admin mode allows users to access higher privileges such as creating shortcuts and other settings in preferences.

Admins set preferences that determine the available customization settings on Launcher devices during AirWatch Launcher Setup. Settings such as: adding a folder, moving an icon, and swapping the position of an icon, folder or widget can be changed by the end user. View the available preferences in the Launcher Device Settings Matrix.

By default, any changes the user makes to the Launcher set up, as allowed by the admin in the device preferences remains on the device in the event the Launcher is reloaded, admin pushes the profile again, or user exits Launcher. If the admin has to re-push the Launcher profile that includes changes to the Launcher preferences, the new profile overrides any changes the user has made only in the case where the configurations conflict. For example, if the user rearranges the icon on the screen and then the admin has disables that feature in the latest version of the profile, the icons revert to the original position. Another example is if the user has moved around the icons as allowed by the admin and then the admin updates the profile so that there is a different icon in one of the positions, the admins icon will be retained at that position.