App compliance

The policy configuration App compliance defines which apps should be available on an iOS device and which should not. In Relution, App compliance can be configured in two different ways.

A misconfiguration can lead to data loss, e.g. if apps are blocked or removed from the device as a result. Admins, customers and the people using the devices are responsible for backing up their own data from individual apps or from the devices.

Creating the Configuration

The configuration is created under Devices → Policies in an iOS policy via Add Configuration → App compliance. In the General section, List type determines whether the apps are treated as a blocklist (Blocklist — The apps below are not allowed, the default for new configurations) or as an allowlist (Allowlist — The apps below are allowed). Only one of the two list types is active per configuration.

The apps are entered via Add in the Blocked apps or Allowed apps section below. The available sources are Relution App Store app, Apple App Store App, iOS System or built-in app and Manually add app (name and bundle ID). The same sources apply to the Required apps section.

The blocklist and the allowlist only take effect on supervised devices: there, blocked or non-allowed apps are hidden. On unsupervised devices, no apps are hidden; if a blocked or non-allowed app is installed there, the device is displayed as Noncompliant.


Blocklist — The apps below are not allowed

This is a classic blocklist. All apps on this list are hidden on supervised iOS devices and users can no longer access them. The apps are not uninstalled. For example, individual system apps or apps from the public App Store that are not allowed to be used on the devices can be stored here.

The system apps Settings and Feedback Assistant cannot be blocked. Likewise, a required app must not be on the blocklist. In both cases, the configuration cannot be saved.

On a Relution Shared Device, this list type only allows the required apps and the user’s auto-deployed apps, minus the blocked apps. No other apps are allowed, see Relution Shared Device →.

Allowlist — The apps below are allowed

This is the classic allowlist. All apps stored here can be installed on iOS devices, are subsequently visible to users and can be used. On supervised devices, all other apps are hidden.

Relution adds some system components automatically: if the Camera app is on the allowlist, the QR code scanner is added as well (QR code cannot be scanned →). If AirDrop is allowed, the AirDrop interface is added as well (AirDrop →).

Three further options are available for the allowlist:

Put all auto-deployed apps on the allowlist

All apps that are stored in the Auto Deployments for corresponding user accounts or groups are automatically added to the allowlist when Put all auto-deployed apps on the allowlist is enabled. This saves effort and avoids errors. The option is disabled for new configurations.

Allow local secret prompts

The option Allow Local Secret Prompts (e.g., iCloud, Google login) adds the system dialogs for local secret prompts and for the Google login to the allowlist. Without this option, such login dialogs are blocked while an allowlist is active. The option is disabled for new configurations.

The Weblinks field determines how web links are handled on the devices (Weblinks →):

  • Don’t allow weblinks
    All web links are blocked - regardless of whether they were brought to the iOS devices via a policy or an action. This is the default setting.

  • Allow all full screen weblinks
    Only web links configured for full screen mode are displayed.

  • Allow all weblinks (Safari will be allowed automatically)
    All web links are allowed. The Safari Browser is enabled automatically.


Required Apps

Apps on this list must be installed on the devices. An app is only actively installed if the checkbox in the Auto install column is selected; it is selected by default when an app is added. Native apps from the Relution Store and App Store apps with device-based licenses from Apps and Books (VPP in the portal) can be installed automatically. Users cannot remove auto-installed required apps from the devices.

If an app on this list is missing on a device, the device is displayed as Noncompliant in the device inventory, provided the option Add compliance violation when required apps are missing is enabled under Settings → Device Management → Device Management (default). The Relution Agent cannot be added to this list. It is automatically installed on devices upon enrollment.

Further columns of the list:

  • Lockable and Hideable: Allow the user to lock or hide the app on the device. Hiding the app also requires it to be lockable. Both checkboxes are selected when an app is added and require iOS 18.1 or newer.
  • VPP licenses and Available VPP licenses: Show the existing and the remaining free Apps and Books licenses per app.

Two toggles are available above the list:

  • Uninstall auto-installed required apps if no longer required: If an auto-installed required app is removed from the configuration, or the configuration is removed from the device, the app is uninstalled. The toggle is off for new configurations.
  • Always put these required apps on the allow list: If this or another policy configures an allowlist for the device, the required apps of this configuration are added to it. The toggle applies regardless of whether a blocklist or an allowlist is selected in this configuration. It is on for new configurations.

If the second toggle is off for an allowlist, all required apps must also be entered on the allowlist; otherwise, the configuration cannot be saved.

In addition, system apps should also not be included on the Required apps list. They do not need to be installed as they are already on the devices. It is enough to add them to the allowlist.


Multiple Configurations on One Device

If several App compliance configurations apply to a device, for example from different policies, they are merged:

  • If all configurations contain a blocklist, the blocklists are combined.
  • If at least one configuration contains an allowlist, all blocklists are ignored and the allowlists are combined.
  • Put all auto-deployed apps on the allowlist and Allow Local Secret Prompts (e.g., iCloud, Google login) only take effect if they are enabled in all configurations with an allowlist.
  • For Weblinks, the most restrictive setting applies.
  • The required apps of all configurations are combined. If Auto install is selected for an app in any of the configurations, it is installed automatically.

How helpful was this article?