Managed App Configuration for MDM Settings


Supported in:

Kiosk Pro Plus and Enterprise

Managed App Configuration allows users to configure app settings remotely through Mobile Device Management (or MDM).

While Managed App Configuration is increasingly supported by MDM providers, it is not a feature included in every MDM solution. To determine if Managed App Configuration is supported by your MDM provider, you’ll need to contact them directly.

To use Managed App Configuration, the app must be installed and/or managed through the MDM. This requires the use of license codes purchased through Apple Business Manager. It is not possible to use Managed App Configuration with apps installed through iTunes, the App Store directly on the device, or Apple Configurator.

MDM solutions operate at the device level, communicating directly with the iOS/iPadOS operating system using standard Apple-provided APIs. When using Managed App Configuration, the MDM service sends a dictionary of settings to the app, which then applies them. This can occur either as a part of the initial app installation or later as a management command.

Settings are defined using key-value type-value sets. A full list of keys, value types and default values for each setting in Plus and Enterprise is maintained here.

How these are inserted depends on the interface of the MDM you are using - options include:

  • individual inputs
  • XML insertion
  • constructed interface via managed schema files

Individual Inputs

Many MDM providers, including Miradore and SimpleMDM, format their Managed App Configuration settings as a series of individual inputs where the user defines the key, value type, and value for each setting:

XML Insertion

Some MDMs, including Jamf Pro, support a single large text field formatted as XML, similar to our Remote Settings Control but with a slightly different format. While this method does generally require a basic understanding of XML, it has the benefit of allowing you to update a large number of settings quickly and efficiently. As an idea of what this looks like, to update the Homepage setting and Idle Time Limit, you would add the following dictionary through your MDM:


You can export this XML configuration from within the app based on the current app settings.

Constructed Interface via Managed Schema File

Other MDM providers use a standardized schema file we provide them to construct a version of the app's settings menu within the MDM interface. Settings can be configured in the same way that they are inside the app via text input, selection dropdown, and toggle switch.

Editing Settings

Supported in:

Kiosk Pro Plus and Enterprise

Settings are defined in most cases using key-value type-value sets. A full list of keys, value types and default values for each setting in Plus and Enterprise is maintained here.

If your MDM supports XML insertion, you can export a file containing the app's current settings from within the app. You can also use these exported files to determine settings for an MDM that requires the entry of individual key-value type-value sets.

Settings that accept text will be filled out in between the <string></string> tags and settings that require a number will use <integer></integer> tags. As an example, to change the homepage setting of the kiosk, you would find the matching key/value pair in the list:


In an MDM that enters values as a set of multiple inputs, like SimpleMDM, this would translate to:

Settings that are toggled either on or off accept <true/> or <false/> values. For example, the Show Address Bar setting (turned On):


In an MDM that enters values as a set of multiple inputs, like SimpleMDM, settings that are toggled either on or off are considered to be boolean values. For example, the Show Address Bar setting (turned On):

Ampersands ('&') are a reserved character in XML. If a URL or another setting requires one, you will need to instead use the unit code ‘&amp;’. This substitution will occur automatically if working with an exported version of settings files.

Customizing Settings for a Specific Device

When applying settings through Managed App Configuration, the majority of MDM's are structured in such a way as to only allow for a single configuration to be applied to all devices being deployed, but it is still often possible to identify a specific device or apply custom settings through token substitution or custom variables.  

Some providers, including Miradore, allow you to create multiple config files to apply to specific devices or groups of devices. 

Most MDM providers now allow token substitution in the settings configuration. This allows a unique identifier to be set based on information the MDM is able to pull about the device, allowing for a large deployment to use unique identifiers without having to manually enter them on each device. While these may vary from vendor to vendor, they generally include:

  • Device Name
  • ID
  • IMEI
  • MEID
  • Model
  • Phone Number, if applicable
  • Serial Number
  • UDID
  • WiFi MAC Address

Each provider may format these device variables differently; please contact your MDM provider directly for additional details.

Certain MDM providers also allow you to set up custom variables that can be defined within the MDM interface and passed to the app, which makes it easy to customize any of the app's settings for a specific device. An overview of what this looks like when using SimpleMDM is available here.

In version 11.1, we loosened type matching for Managed App Configuration to better support MDMs that only allow passing custom variables as string-type values.  If Kiosk Pro can match a string that is passed to a possible valid value, that value will be applied regardless of the value type defined – for example, passing the strings ‘true’ or ‘1’ to a setting that uses a boolean value type will be successfully matched.  This makes customizing the app’s settings for a specific device or group of devices much more flexible.  

Export Current Settings

Supported in:

Kiosk Pro Plus and Enterprise

Export your current Kiosk Pro settings as a formatted list of key-value pairs for use in Managed App Configuration. Settings are exported in the .xml format used by MDMs that allow you to add all settings by copy and pasting into a single text field (like JAMF Pro).

You have a couple options for how the file is exported:

  • Save - Save the file on the device to transfer to your computer using iTunes.
  • Email - Email the file to yourself. This requires a Mail account to be set up on the iPad.
  • Share - AirDrop the file to another Apple device, or transfer to another app. More info below.

You also have the option to export a file with only the settings you've made changes to.

There are a couple of settings not included in an exported list - specifically the SMTP password (for security), the Unique iPad ID, and the Kiosk Name and Unit Name for the Remote Management Server (to prevent accidentally overwriting with the values from the original device).

If you need to set any of these values through Managed App Configuration, you can configure these settings manually using the key-value set from our spreadsheet and/or our documentation for that specific setting.

To export the settings:

  1. Open the Kiosk Pro settings on the iPad that is correctly configured.
  2. Scroll down to the Remote Update category and select Remote Settings Control.
  3. Select Export & Transfer Current Settings.
  4. Select Export All Settings or Export Changed Settings Only.
  5. Select "Save" if you want to transfer the file to your computer. A file called "mdm_settings.xml" will be created in the Kiosk Pro documents folder on the iPad.
  6. Select "Email" if you want to email the file. A window will appear allowing you to create an email, and the file will be deleted from the documents folder after being sent.
  7. Select "Share" if you want to transfer the file via AirDrop, or to another app. More info below.

Change Log

Added to Enterprise in version 7.1, added to Plus in version 7.5.1.  Loosened type matching as described above in version 11.1

Still stuck? How can we help? How can we help?