Overview of [email protected] for iOS

The [email protected] app gives device users an intuitive and secure way to access, store, view, edit, and annotate documents from content repositories, such as Microsoft SharePoint, and cloud services such as Box and Dropbox. It allows administrators to configure content repositories, which are then automatically available to device users. It also lets administrators establish data loss prevention controls to protect documents from unauthorized distribution. [email protected] supports AES-256-GCM for encrypting email attachments.

Device users must have a valid user ID and password to access content sites.

The [email protected] consists of the following elements:

Table 1. [email protected] elements

Section

Description

Sites

The [email protected] dashboard displays the content sites.

My Files

Save files to My Files for viewing and editing. Unlike other folders, documents in My Files are not connected to any content site and are not updated automatically.

Starred

Files and folders marked as starred are available here.

Offline

Files marked as offline are available for offline

[email protected] features

The device users can use the following [email protected] features:

  • Log in to content repositories and navigate through folders.
  • Download documents from content repositories.
  • View documents.
  • Edit and annotate local files.
  • Upload documents to content repositories.
  • Download, view, and email encrypted attachments.
  • Add content repositories to [email protected]

A Ivanti license is required for deploying [email protected] [email protected] uses certain aspects of AppConnect, including passcode access and app tunneling. However, an AppConnect license is not required for [email protected]

[email protected] for iOS is an AppConnect-enabled app. AppConnect containerizes apps to protect content on iOS and Android devices. Each AppConnect app becomes a secure container whose content is encrypted and protected from unauthorized access. Because each user has multiple business apps, each app container is also connected to other secure app containers. This connection allows the AppConnect apps to share content. AppConnect apps are managed using policies configured in Unified Endpoint Management (UEM) platform. The UEM platform is either Ivanti EPMM or Ivanti Neurons for MDM.

As an AppConnect app, all [email protected] content is secured. The app interacts with other apps according to the data loss prevention policies that you specify. The app has the following secure features:

  • Secure apps passcode: A secure apps passcode, if you require one, protects access to all secure apps. This is the AppConnect passcode, which you define in UEM. The AppConnect passcode provides an additional layer of security for secure apps, beyond the device passcode.
  • Data encryption: AppConnect encrypts all AppConnect-related data on the device, such as [email protected] app data, app configurations, and policies. This means app data is secure even if a device is compromised.
  • Data loss prevention: You determine whether [email protected] for iOS can use the iOS copy/paste , open-in features. AppConnect data loss prevention policies control if users can copy/paste data out of [email protected] and control how email attachments can be shared with other apps via open-in.

For information about AppConnect features and configuration beyond [email protected] for iOS, see the Ivanti AppConnect Guide for EPMM and Ivanti Tunnel for iOS Guide.

Enable Access for [email protected]

In Ivanti EPMM and Access as a service deployment, federated traffic from [email protected] through Access is only supported with Tunnel. However, using Tunnel to CIFs services will fail.

Federated traffic through AppTunnel and Access as a service is not supported for [email protected] Selecting Enable Access option in the [email protected] configuration has no impact.

For information about Access and how to set up the service with Ivanti EPMM, see the Ivanti Access Guide.

If Enable Split Tunneling using Tunnel is selected, HTTPS authentication traffic, which would have previously used AppTunnel to Access, goes through Tunnel instead.