Category filter

Configuration profile for iOS app lock mode

Typically, organizations like schools and businesses want to limit how their pupils or employees can use their iOS devices to only the one app that is necessary for them. This can be achieved by deploying a custom configuration profile. Hexnode allows IT admins to remotely deploy this configuration profile to multiple iOS devices enrolled in the UEM via the Deploy Custom Configuration feature.


The configuration profile provided below is adapted from a third-party open-source site.


This configuration profile is supported on supervised devices running iOS 6.0 and later.

Configuration profile to lock the device to a single app

In the configuration profile, specify the bundle ID of the app you want to lock the device down to.


  • You can find the bundle ID of preinstalled iOS apps here.
  • From the endpoint, you can choose to locate the app bundle ID on iTunes Connect. From iTunes Connect, navigate to ‘My Apps’ and select the app. The app information page will contain the bundle ID.
  • Make sure you install the target app on the device before deploying the configuration profile.

What happens at the device end?

Once the policy and custom configuration are associated, the specified app automatically launches on the device and cannot be exited until the profile is removed. The home button is in a disabled state, and the device returns to the app automatically upon waking or restarting. You also no longer have access to the Control Center, settings app, and notifications, even from the lock screen.


  • To create and customize configuration profiles, you can use tools like Apple Configurator, Profile Manager or manually create them using text editors.
  • Use non-encrypted .mobileconfig, .xml, or plist files to deploy profiles across iOS devices.
  • Ensure that you do not associate conflicting configurations with the devices.
  • Use wildcards to fetch key values from the portal.
  • It is recommended to manually validate the configuration profile execution on a system before executing the action in bulk.
  • Hexnode will not be responsible for any damage/loss to the system on the behavior of the configuration profile.

  • Configuration Profile Repository