Relution Signet Customer Hub

App Compliance

Android Classic / Legacy allows Native Apps to be uploaded as .apk files to the Relution App Store and distributed to enrolled Android devices via action or policy. Distribution via action is described under Deploy Relution Store App →.

Native apk via a policy

This method does not provide automatic updates for new app versions.

First, the app is deployed to the Relution App Store, then distributed via a policy with the App compliance configuration.

  1. In the Relution portal, the menu item Apps → App Store is opened and a new app is added via Add.
  2. The option Native app is selected, followed by Next.
  3. Under Choose file, the desired .apk file is selected via Select.
  4. On the following page, the release status of the app must be changed from Development (blue icon) to Release (green icon). The change is confirmed with Save.
  5. Under Devices → Policies, a new policy is created via Add. An Android policy is created and given a Name. The policy is saved via Save.
  6. Via Add, the App compliance option is selected, followed by Add details.
  7. The List Type is preselected as Blocklist — The apps below are not allowed by default. Regardless of this, the desired apps from the Relution App Store are added under Required apps.
  8. The configuration is saved and the current version of the policy is published.
  9. To apply the policy to Android devices, the desired devices are added via the Devices with this policy tab. The devices are assigned to an existing static device group with this policy or to a newly created static device group. The selected settings and apps are then automatically applied or installed on the devices.

Selecting Auto install installs the respective apps automatically on the Android devices. For the installation, the devices must be assigned to users who are members of the AppStore User user group.

Configuration settings

The App compliance configuration is divided into three sections.

General

  • Enforce block / allowlist only while roaming – the blocklist or allowlist is only applied while the device is roaming. If the option is switched off, the list applies regardless of the roaming state.
  • Ignore block / allowlist while on a wireless network – only available if the previous option is enabled. While the device is connected via Wi-Fi, apps are allowed even when roaming.
  • List Type – Blocklist — The apps below are not allowed (default) or Allowlist — The apps below are allowed.

For an allowlist, Non-allowed apps defines how all other apps are handled:

  • Uninstall – the user is prompted to uninstall the app from the device. The option is not available if Enforce block / allowlist only while roaming is enabled.
  • Disable – the app remains installed but can no longer be started by the user.
  • Block internet access – revokes the app’s internet access. The option has no effect on pre-installed apps, and some apps may crash as a result; in that case, Disable is preferable.

Blocked or allowed apps

Depending on the List Type, the section is called Blocked apps or Allowed apps. Apps can be added from the Relution App Store, from the Google Play Store or manually via their package name.

The Disable system apps option attempts to block all system and pre-installed apps. This includes the phone app, so emergency calls can no longer be made. If telephony is required, the phone app has to be put on the allowlist.

Required apps

The apps entered here must be installed on the device, otherwise the device is considered noncompliant. Google Play Store apps must be installed by the user; Auto install is only possible for native apps from the Relution App Store.

The configuration is rejected on saving if

  • an app is on the blocklist and under Required apps at the same time, or
  • a weblink is entered as a required app.