Managed App Configurations let you remotely configure settings within managed Apple apps — without touching each device individually. Whether you need to push a license key, set preferences, or lock down application behavior, this feature puts you in control of how apps behave across your fleet.
Overview
A Managed App Configuration is a set of key/value pairs that gets delivered to an app at install time or on demand. The available settings are defined by the app's developer and vary by application — from a simple license key activation to complex behavioral controls.
In Addigy, you can deploy Managed App Configurations in two ways:
- GoLive — Deploy a configuration to a single device on demand.
- Policy — Automatically deploy a configuration to all devices in a policy group.
Configurations are saved per application and shared across both deployment methods — so a configuration created in GoLive is available when assigning via policy, and vice versa, as long as they share the same Apps & Books location token.
Prerequisites
- The app must be available in your Apple Apps & Books library and assigned to a location token in Addigy.
- You must know the configuration keys supported by the app. Refer to the app developer's documentation for available keys. Here is an example of settings for the Zoom app for iOS and iPadOS.
How to Deploy a Managed App Configuration via GoLive
Use this method to configure and deploy an app to a single device immediately.
- Navigate to the GoLive page for the target device.
- Select the Software > Apple Apps tab, then choose the appropriate location token from the dropdown.
-
Find the desired app, click the ellipsis (...) in the Action column, and select Configuration.
-
In the Configuration Overview modal, click Add Configuration.
- Enter the required key/value pairs for each setting you want to configure. Use the table below as a reference for value formatting.
| Key | Type | Example Value |
|---|---|---|
Float |
Float | 5.00 |
boolean |
Boolean | True |
orgID |
String | {{.OrgID}} |
serialNumber |
String | {{.Fact "serial_number"}} |
userName |
String | {{.User "user_name"}} |
You can use Device Facts or End User Attributes as dynamic variables in your configuration values (as shown in the orgID, serialNumber, and userName examples above). See Using Device Facts as Variables and Using End User Attributes as Variables for details.
- Click Save, then close the Configuration Overview modal.
- Click the ellipsis (...) for the same app again and select Deploy.
- Choose one of the following deploy options, then click Deploy:
- App with Configuration — Installs the app and applies the configuration.
- Configuration Only — Applies the configuration to an app that is already installed on the device.
How to Deploy a Managed App Configuration via Policy
Use this method to automatically push an app configuration to all devices within a policy. Configurations assigned at the policy level apply consistently at every regular policy deployment.
- Navigate to the desired policy and select the Software > Apple Apps tab.
- Locate the app you want to configure. The App Configuration column displays a status indicator:
- Green dot — A configuration is already assigned.
-
Grey dot — No configuration is currently assigned.
- Click Configuration in the App Configuration column to open the Configuration Overview modal.
- If no configuration exists yet, click Add Configuration and follow the same key/value steps as described in the GoLive section above.
-
After adding the configuration, click Assign to enable it for this app in the policy.
- Once assigned, click Add/Remove > Add to policy to include the app and its configuration in the policy.
The App Configuration column will show a green dot confirming the configuration is active. From this point on, any device in the policy will receive the configuration when the app is installed with the next regular policy deployment.
Notes:
- If the app is already assigned to the policy, you must remove it before making changes to its configuration. Un-assign the app, update or assign the configuration, then add the app back to the policy.
- Managed App Configurations assigned at the policy level apply across all policies that share the same Apps & Books token.
How to Remove a Managed App Configuration
Removing a Configuration from a Policy
- Navigate to the policy and select the Software > Apple Apps tab.
- Locate the app and click Configuration in the App Configuration column.
- In the Configuration Overview modal, click Remove to un-assign the configuration.
- Close the modal. The App Configuration column will now show a grey dot, confirming no configuration is applied.
Note: You cannot remove a configuration while the app is actively assigned to the policy. Un-assign the app first, remove the configuration, then re-add the app if needed.
Removing a Configuration from a Single Device via GoLive
- Navigate to the device's GoLive page and select the Software > Apple Apps tab.
- Select the appropriate location token from the dropdown.
- Click the ellipsis (...) for the app and select Configuration.
- In the Configuration Overview modal, click Add/Remove Keys.
-
Remove the desired keys by clicking the X next to each one, then click Save and confirm the removal with the Remove Configuration button.
- Close the modal, then click the ellipsis (...) again and select Deploy.
- Choose App Only and deploy to the device.
Note: The app must be closed and reopened on the device for it to revert to its default settings.
Frequently Asked Questions
Can I reuse the same configuration across multiple policies?
Yes. Configurations are saved per application and shared across GoLive and all policies that use the same Apps & Books location token. Assigning a configuration in one policy makes it available to assign in others.
What key/value pairs does my app support?
Available configuration keys are defined by the app developer. Refer to the developer's documentation for a list of supported keys and expected values.
Can I use dynamic values like device serial numbers in a configuration?
Yes. Addigy supports Device Facts and End User Attributes as variables within configuration values. See Using Device Facts as Variables and Using End User Attributes as Variables for syntax and usage.