MobileIron AppConnect vs. Android Enterprise
Threema Work supports Android Enterprise (formerly known as Android for Work). For technical reasons, MobileIron AppConnect and Android Enterprise can’t be used at the same time.
However, Threema MDM can be used to manage the Threema Work app separately in case you use MobileIron AppConnect.
You can deploy the Threema Work app manually or by using an MDM or EMM system:
- Manual deployment: unmanaged devices (without MDM)
Manual deployment is straightforward. After the users have downloaded the free Threema Work app from the appropriate app store, they enter the credentials you have provided, and the app is ready for use. Learn more…
- Deployment via MDM system
If you deploy the Threema Work app via MDM system, the credentials for the app’s activation are provided by the MDM system. The setup process can also be completed automatically using configuration parameters. Learn more…
Learn how to deploy the Threema Work app to your users.
The Threema Work app must be activated using credentials before it is ready for use. Depending on whether the app is deployed manually or via MDM system, the process of defining credentials differs slightly.
Manual deployment (unmanaged devices): individual credentials / single-user licenses
When deploying the Threema Work app manually to unmanaged devices, individual credentials (single-user licenses) are appropriate, which means that each user gets separate credentials to activate the app. If you would use the same credentials for different users (multi-user license), you could not withdraw a user’s access to the app by deleting their credentials or preconfigure the app using Threema MDM.
Deployment via MDM system (managed devices): global credentials / multi-user license
When deploying the Threema Work app using an MDM system, the credentials are distributed along with the app. The preconfiguration of the app is carried out directly in the MDM system, where you can, for example, activate contact synchronization, link a phone number, or set the user’s first and last name (learn more). When deploying the app using an MDM system, you don’t need to define different credentials for each user. Simply use the same username/password pair as multi-user license for all users. If staff changes occur, an individual user’s access to the app can be withdrawn via the MDM system.
Threema Work can be deployed to the intended users in a few simple steps. Then, it must be activated using credentials, and it’s ready for use.
- Finding and defining credentials
- Trial: Credentials have been created for you automatically. Find them in the Threema Work management cockpit.
- New subscription: To set the credentials in the Threema Work management cockpit, navigate to “Credentials > Activate credentials”.
- Download the app
Instruct users to download the free Threema Work app from an app store. You can also place the APK version of the app at your Android users’ disposal.
- Enter credentials (activate the app)
In order to activate the app, your users need to enter the credentials you have specified above. Alternatively, the app can be unlocked using an activation link. Learn more about activation links…
Using Threema MDM, you can even preconfigure the app for your users. This way, you can make sure that the first and the last name is set, the correct phone number or email address is linked, and more. Details…
The “First Steps” PDF will guide you through the manual distribution and activation of the app.
Threema Work supports Android Enterprise (Android 5.0 or higher) and Managed App Configuration (iOS 8.0 or higher). These standards are used by all popular MDM systems (cf. Supported MDMSystems).
A wide range of MDM parameters allow you to preconfigure the app tailored to your company’srequirements.
Rollout and configuration using a regular MDM system
Configuration using Threema MDM
Configure the app easily in the Threema Work management cockpit also when lacking an additional MDMsystem. Details
Threema MDM in addition to a regular MDM system
Threema MDM can be used in addition to a regular MDM system, e.g. to push last-minute changes.
MDM parameters set in Threema MDM overwrite parameters set by the MDM system. This applies also toindividual values. For example, if only one parameter is set in Threema MDM, only this one parameterwill be overwritten, while the rest of the configuration defined in the MDM system remainsunchanged.
You can preconfigure the Threema Work app for your users and set it up as desired so that the app is ready for use when first launched. The preconfiguration can be carried out either using a regular MDM system or using Threema MDM. Threema MDM is typically used for unmanaged devices, where individual credentials come into play (this way, users can be identified and managed individually).
For users with individual credentials, “individual values” can be set in Threema MDM. Individual values are values that are typically different among different users, e.g., name, nickname, phone number, etc.
Find out how to preconfigure the Threema Work app using Threema MDM.
Threema Work is compatible with any MDM system that supports Android Enterprise (Android) and Managed App Configuration (iOS). Many developers of such MDM systems are part of the AppConfig Community. Threema Work is compatible with MobileIron, Sophos Mobile, Citrix XenMobile, SAP Afaria, VMware AirWatch, and others.
The following step-by-step instructions for deploying Threema Work are available:
Other MDM systems: Please make sure that your MDM system supports Android Enterprise (Android) and Managed App Configuration (iOS).
With Android Enterprise, it is generally possible to distribute the app in a container. iOS does not have a standardized type of container supported by the operating system.
However, Threema Work is not available as a wrapped container solution (e.g., for MobileIron AppConnect or Citrix MDX Toolkit). Wrapping would require substantial adjustments to the Threema Work app that would lead to considerable limitations and incompatibilities. Since our requirements in regard to ease of use and reliability could not be met, wrapping is not supported.
If your company uses MobileIron AppConnect, please refer to this article.