Enterprise Mobility Management

Use Enterprise Mobility management to provide an extra level of security compliance

Medallia Mobile apps provide an extra level of security compliance through interoperation with the most popular Enterprise Mobility Management (EMM) suites. EMM is the set of people, processes, and technology focused on managing mobile devices. As more workers have bought smartphone and tablet computing devices, and have sought support for using these devices in the workplace, EMM has become increasingly significant in addressing the associated security concerns.

Every EMM vendor has a different system, menus, and methods for configure managed devices. Your company's IT team must work with your chosen EMM vendor to configure EMM at your company.

Note: These requirements apply to Android devices:
  • Your company must first sign up for Android in the enterprise and choose an EMM provider. For more information, see Android Enterprise and Android Enterprise Help.
  • Medallia Mobile apps support EMM on devices with Android 5.0 Lollipop and later (those that have work profile support).
  • Personal devices need a Google Account with Google Play installed.
  • Your EMM provider might require you to install a device policy controller application.
Important: Medallia does not distribute IPA or APK files, or any unpublished app.

AppConfig Community

AppConfig Community is a collection of EMM solution providers that make it easier for developers and customers to drive mobility in business. With AppConfig Community tools and best practices, developers do not require EMM-specific integrations for many enterprise use cases. Users also benefit from automated features such as an out-of-the-box experience that provides instant app access without the need for setup flows or user credentials. For more information, see AppConfig Community.

Medallia Mobile and Medallia Voices (version 2.0 and later) enable providers that support the native AppConfig standard. This standard has been adopted by the most popular vendors, such as:

  • VMWare AirWatch
  • MobileIron
  • IBM MaaS360
  • SOTI
  • BlackBerry/Good (UEM 12.6 and later)
  • InTune
  • Any other vendor who support the AppConfig standards

AppConfig capabilities for iOS

You can use AppConfig to deploy Medallia Mobile apps remotely. Additionally, apps support these AppConfig capabilities for iOS:

CapabilitySummary of AppConfig Community best practices
App ConfigurationUse Managed Configuration to set the CompanyID into the app automatically.
App TunnelLeverage the Per-app VPN capability available in most commercial VPN solutions, and in iOS 9+. No development is required.
Single Sign-OnImplement a standard SSO protocol, and invoke the identity provider login page in a web view.
App Security — Managed Open-InSet the managed open in control available from the EMM provider to restrict the native open in capability. No development is required.
App Security — Prevent App BackupSet the prevent app backup security control available from the EMM provider to prevent app data backup in iTunes. No development is required.
App Security — Disable Screen CaptureSet the prevent screen capture security control available from the EMM provider, and in iOS 9+ to restrict the native screenshot capability. No development is required.
App Security —Remotely Wipe AppDistribute the app to the device as a managed application using your EMM provider's tools to gain the ability to remotely wipe the app from the device. No development is required.
App Security — Disable Copy-PasteUse the iOS 7+ Managed App Configuration to set the copy/paste policy on the app.

AppConfig capabilities for Android

Medallia Mobile apps support these additional AppConfig capabilities for Android:

CapabilitySummary of AppConfig Community best practices
App ConfigurationDevelop Android 5.0+ App Restrictions into the app. You can set the CompanyID into the app automatically.
App Tunnel/Per-App VPNLeverage the Per-App VPN capability available in most commercial VPN solutions, and in Android 5.0+. No development is required.
App Security — Disable Screen CaptureUse an Android 5.0+ managed profile to prevent screenshots. No development is required.
App Security — Enforce App EncryptionEnrolled devices are encrypted as part of the enrollment process. No development is required.
App Security — Remotely Wipe AppDistribute the app to the device as a managed application using your EMM provider's tools to gain the ability to remotely wipe the app from the device. No development is required.
App Security — Disable Copy-PasteUse an Android 5.0+ managed profile to limit copy/paste to managed applications only. No development is required.

The kMMCompanyIdentifier attribute key

Medallia Mobile apps support the kMMCompanyIdentifier AppConfig XML attribute key for iOS and Android devices. This code shows a sample property-list configuration XML file with this key in its correct location:

<managedAppConfiguration>
  <version>1</version>
  <bundleId>com.medallia.mm3</bundleId>
  <dict>
    <string keyName="kMMCompanyIdentifier">
      <defaultValue>
        <value></value>
      </defaultValue>
    </string>
  </dict>
  <presentation defaultLocale="en-US">
    <field keyName="kMMCompanyIdentifier" type="input">
      <label>
        <language value="en-US">Company Identifier</language>
      </label>
      <description>
        <language value="en-US">Enter your Company Identifier for Medallia.</language>
      </description>
    </field>
  </presentation>
</managedAppConfiguration>

Use a non-default email client

By default, forwarding an email from a Medallia Mobile application uses the mobile device's native email client, which might include use of the user's personal email address. Additionally, some companies require the use of specific enterprise email clients, which might differ from the defaults on mobile devices. To resolve these issues, Medallia Experience Cloud supports the mailto URI scheme for modifying the default email client and its configuration.

Each email client has a specific scheme that is mapped to Medallia Mobile application attribute keys, so the apps to pass parameters to the email client. If your company wants to specify a non-default email client (BlackBerry, Boxer, Citrix, Gmail, and Outlook), use the AppConfig capabilities in the table. For more information, see Mobile Cross-Platform.

CapabilityDescription
MMMailUrlSchemeThe mailer URL scheme that is used to launch the client email app.
MMMailRecipientParameterNameThe parameter to pass the email recipient list to the email client.
MMMailBccParameterNameThe parameter to pass the email BCC list to the email client.
MMMailCCParameterNameThe parameter to pass the email CC list to the email client.
MMMailSubjectParameterNameThe parameter to pass the email subject to the email client.
MMMailBodyParameterNameThe parameter to pass the email body to the email client.

For example:

<managedAppConfiguration>
   <version>1</version>
   <bundleId>com.medallia.mm3</bundleId>
   <dict>
      <string keyName="kMMCompanyIdentifier">
         <defaultValue>
            <value></value>
         </defaultValue>
      </string>
   </dict>
   <presentation defaultLocale="en-US">
      <field keyName="kMMCompanyIdentifier" type="input">
         <label>
            <language value="en-US">Company Identifier</language>
         </label>
         <description>
            <language value="en-US">Please enter your Company Identifier for Medallia.</language>
         </description>
      </field>
   </presentation>
   <dict>
       <string keyName="MMMailUrlScheme">
           <defaultValue>
               <value></value>
           </defaultValue>
       </string>
   </dict>
   <presentation defaultLocale="en-US">
       <field keyName="MMMailUrlScheme" type="input">
           <label>
               <language value="en-US">Mail Url Scheme</language>
           </label>
           <description>
               <language value="en-US">Please enter your Mailer URL Scheme for Medallia.</language>
           </description>
       </field>
   </presentation>
   
   <dict>
       <string keyName="MMMailRecipientParameterName">
           <defaultValue>
               <value></value>
           </defaultValue>
       </string>
   </dict>
   <presentation defaultLocale="en-US">
       <field keyName="MMMailRecipientParameterName" type="input">
           <label>
               <language value="en-US">Recipient FieldName</language>
           </label>
           <description>
               <language value="en-US">Please enter the recipient email field.</language>
           </description>
       </field>
   </presentation>
   
   <dict>
       <string keyName="MMMailBccParameterName">
           <defaultValue>
               <value></value>
           </defaultValue>
       </string>
   </dict>
   <presentation defaultLocale="en-US">
       <field keyName="MMMailBccParameterName" type="input">
           <label>
               <language value="en-US">Bcc FieldName</language>
           </label>
           <description>
               <language value="en-US">Please enter bcc email fields separated by commas.</language>
           </description>
       </field>
   </presentation>
   
   <dict>
       <string keyName="MMMailCCParameterName">
           <defaultValue>
               <value></value>
           </defaultValue>
       </string>
   </dict>

Specifying a browser for authentication

Some companies require that only certain browsers can be used for authentication. To assist with this requirement, Medallia supports these AppConfig XML attribute keys for iOS and Android devices:

KeyDescription
kMMIOSHttpsBrowserSchemeThe browser to use for secure HTTP on iOS devices. Common values include:
  • safari-https
  • googlechrome
  • firefox://open-url?url=
  • microsoft-edge-https
  • opera-https
kMMIOSHttpBrowserSchemeThe browser to use for non-secure HTTP on iOS devices. Common values include:
  • safari-http
  • googlechrome
  • firefox://open-url?url=
  • microsoft-edge-http
  • opera-http
kMMAndroidOAuthBrowserPackageNameThe package name of the browser to use for Android devices. Common values include:
  • com.android.chrome
  • org.mozilla.firefox
  • com.microsoft.emmx
  • com.opera.browser
kMMAndroidOAuthBrowserVersionThe minimum version of the browser to use for Android devices.
kMMAndroidOAuthBrowserSignatureThe signature hash for the browser to use for Android devices.

Consider using this XML snippet to assist you when specifying browsers with AppConfig for iOS:

<managedAppConfiguration>
	<version>1</version>
	<bundleId>com.medallia.voices2</bundleId>
	<dict>
		<string keyName="kMMIOSHttpsBrowserScheme">
		</string>
		<string keyName="kMMIOSHttpBrowserScheme">
		</string>
	</dict>
	<presentation defaultLocale="en-US">
	<fieldGroup>
		<name>
			<language value="en-US">iOS</language>
		</name>
		<field keyName="kMMIOSHttpsBrowserScheme" type="input">
			<label>
				<language value="en-US">HTTPS Auth Browser Scheme</language>
			</label>
			<description>
				<language value="en-US">Enter the HTTPS Scheme for browser authentication</language>
			</description>
		</field>
		<field keyName="kMMIOSHttpBrowserScheme" type="input">
			<label>
				<language value="en-US">HTTP Auth Browser Scheme</language>
			</label>
			<description>
				<language value="en-US">Enter the HTTP Scheme for browser authentication</language>
			</description>
		</field>
	</fieldGroup>
	</presentation>
</managedAppConfiguration> 

Consider using this XML snippet to assist you when specifying browsers with AppConfig for Android:

<managedAppConfiguration>
	<version>1</version>
	<bundleId>com.medallia.voices2</bundleId>
	<dict>
		<string keyName="kMMAndroidOAuthBrowserPackageName">
		</string>
		<string keyName="kMMAndroidOAuthBrowserVersion">
		</string>
		<string keyName="kMMAndroidOAuthBrowserSignature">
		</string>
	</dict>
	<presentation defaultLocale="en-US">
	<fieldGroup>
		<name>
			<language value="en-US">Android</language>
		</name>
		<field keyName="kMMAndroidOAuthBrowserPackageName" type="input">
			<label>
				<language value="en-US">Browser Package Name</language>
			</label>
			<description>
				<language value="en-US">Enter the browser package name for authentication</language>
			</description>
		</field>
		<field keyName="kMMAndroidOAuthBrowserVersion" type="input">
			<label>
				<language value="en-US">Browser version</language>
			</label>
			<description>
				<language value="en-US">Enter the browser version for authentication</language>
			</description>
		</field>
		<field keyName="kMMAndroidOAuthBrowserSignature" type="input">
			<label>
				<language value="en-US">Browser signature</language>
			</label>
			<description>
				<language value="en-US">Enter the browser signature for authentication</language>
			</description>
		</field>
	</fieldGroup>
	</presentation>
</managedAppConfiguration> 

Add Medallia Mobile to AirWatch

Complete these steps to add Medallia Mobile to AirWatch for iOS and Android. Ensure you have administrator access to AirWatch before attempting any configuration. For more information about app distribution with AirWatch, see the official AirWatch documentation.

  1. In the AirWatch portal, navigate to Apps & Books > Applications > Native > Public.
  2. Click Add Application.
  3. In the Platform field, select Android or iOS, as appropriate.
  4. In the Source field, select Search App Store, and then search for Medallia.

    If the search cannot find Medallia Mobile, Android, it might not be approved for your organization. You can approve Medallia Mobile in the Google Play store.

  5. Next to the Medallia Mobile search result, click Select.
  6. Click Save & Assign.
  7. Click Add Assignment.
  8. Click Assignment Group.
  9. From the Assignment Group list, select Application Configuration Policy.
  10. From the Application Configuration field, select Enabled.
  11. In the Application Configuration section, enter this information:
    Configuration keyValue typeConfiguration value
    kMMCompanyIdentifierStringAdd full instance companyidURL
  12. If your company requires a specific email client, add the configuration keys as described in Use a non-default email client, above.
  13. Click Add.
  14. Click Save & Publish.
  15. Click Publish.

    After adding Medallia Mobile to AirWatch, it appears in the Apps & Books > Applications > Native > Public section of the AirWatch portal.

Add Medallia Mobile to BlackBerry UEM

Complete these steps to add Medallia Mobile to BlackBerry UEM. For more information about BlackBerry, see the official BlackBerry UEM documentation.

  1. In the BlackBerry UEM portal, select Apps.
  2. Click the Add an App icon.
  3. Click App Store or Google Play, as appropriate.

  4. From the Country list, select your country.

  5. In the Search field, enter Medallia.

  6. In the search result, click the Add button next to Medallia Mobile.

  7. In the App Configuration section of the App Options page, click the Add icon to add a default instance.

  8. Click Configure Manually.

  9. In the Name field, enter a name for the configuration.

  10. Enter this information:
    Configuration keyValue typeConfiguration value
    kMMCompanyIdentifierStringAdd full instance companyidURL
  11. If your company requires a specific email client, add the configuration keys as described in Use a non-default email client, above.
  12. Click Save, and then click Add.
  13. Assign the app to users or groups, using the name you assigned in the App Configuration section.
    Important: For the app configuration to be applied to Medallia Mobile for Android, use the Work and personal - user privacy (Android for Work) or Work and personal - user privacy (Android for Work - Premium) activation policy. If you use the MDM control activation policy you cannot apply the app configuration.

    After adding Medallia Mobile to BlackBerry UEM, it appears in the Work Apps section of the BlackBerry UEM portal.

Add Medallia Mobile to Citrix XenMobile

Complete these steps to add Medallia Mobile to Citrix XenMobile. For more information about Citrix, see the official Citrix documentation.

  1. In the XenMobile console, select Configure > Apps.
  2. Click Add, and then select Public App Store.
  3. In the App Information pane, configure this properties, and then click Next:
    • Name
    • Description
    • App Category
  4. In the Platforms section, select the platforms that are applicable to your distribution plan, such as:
    • iPhone
    • iPad
    • Android for Work
  5. For each platform, complete these steps:
    1. In the search bar, search for Medallia.
    2. Click Medallia Mobile 3 tile.

      The App Details fields are populated with information related to the app.

    3. Configure the deployment rule depending on your organizations deployment plan, and then click Next.
      Note: If Android for Work cannot find Medallia Mobile, the application might not be approved for your organization. You can approve it in the Google Play store.
  6. Click Next.
  7. For iOS devices, you can install Medallia Mobile on devices from the Citrix Hub app. For Android, Medallia Mobile appears in the Google Play Store, managed by your Android Work Profile.

Add Medallia Mobile to MobileIron

Complete these steps to add Medallia Mobile to MobileIron. For more information about MobileIron, see the official MobileIron documentation.

  1. In the MobileIron portal, navigate to Apps > App Catalog.
  2. Click Add.
  3. In the search menu list, select either Apple App Store or Google Play Store, as appropriate, and then search for Medallia.
  4. Select Medallia Mobile in the search result, and then click Next.
  5. Optionally, describe the app and add images.

  6. Select one of these distribution levels for this distribution of the app, and then click Next:

    • Everyone — The app is added to all user-compatible devices
    • No one — The app is staged for distribution at a later date
    • Custom — The app is distributed only to users or groups you choose
  7. In the App Configuration Summary section, click the Add icon next to either iOS Managed App Configuration or Managed Configurations for Android, as appropriate.
  8. In the Name field, enter a name for the configuration.

  9. Enter this information:
    Configuration keyValue typeConfiguration value
    kMMCompanyIdentifierStringAdd full instance companyidURL
  10. If your company requires a specific email client, add the configuration keys as described in Use a non-default email client, above.
  11. Click Next, and then click Done.

    After adding Medallia Mobile to MobileIron, it appears in the Apps Catalog section of the MobileIron portal.