Docs@Work 2.0.

0 for
Android enterprise (Android for Work)
May 18, 2017

This document contains the setup information required for Docs@Work for Android enterprise.
• Overview
• Support and compatibility
• What’s New
• Before you begin
• Adding and configuring Docs@Work for Android enterprise
• Generating Group and Published site configuration
• Add attachments from Docs@Work in an Email
• What users see

Proprietary and Confidential | Do Not Distribute

Overview
The Docs@Work app gives device users an intuitive 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.

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

The device users can:

• 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.
• Add content repositories to Docs@Work.

This document addresses the setup required for Docs@Work with Android enterprise.

Support and compatibility

For information on support and compatibility, see the MobileIron Docs@Work for Android and Android enterprise
Release Notes.

What’s New
• Support to add attachments in an email from Docs@Work when you compose an email from Email+ or any
other email client. See “Add attachments from Docs@Work in an Email” on page 7.

Before you begin

Prerequisites
• MobileIron Core must be set up for Android enterprise. For more information, see the MobileIron Core Device
Management Guide for Android enterprise.
• Tunnel for Android enterprise should be set up and devices should be enrolled with Android enterprise with
Tunnel. For more information, see How to Set Up App VPN with MobileIron Tunnel for Android enterprise.
• Device users must enable MobileIron Tunnel before using Docs@Work to access corporate resources.

Docs@Work 2.0.0 for Android enterprise (Android for Work) | 2

Limitations
The following are limitations of Docs@Work for Android enterprise:
• Only one Docs@Work app configuration for Android enterprise can be configured per MobileIron Core. You
cannot have multiple Docs@Work configurations assigned to different labels.
• Access to CIFS and DFS repositories is not supported.
• Single sign-on using Kerberos constrained delegation is not supported.
• AppTunnel and access through Standalone Sentry is not supported.
• Cert-based auth for SharePoint is not supported.

Configuration tasks overview

These configuration tasks are performed in the MobileIron Core Admin Portal:
• “Adding and configuring Docs@Work for Android enterprise” on page 3
• “Generating Group and Published site configuration” on page 7

Adding and configuring Docs@Work for Android

enterprise
Upload the MobileIron Docs@Work for Android enterprise app to MobileIron Core from Google Play and configure
content sites to make it available to Android enterprise devices.

To add and configure Docs@Work for Android enterprise:

1. In the MobileIron Core Admin Portal, go to Apps > App Catalog.
2. Click Add+.
3. Click Google Play.
4. For Application Name, enter Docs@Work for Android enterprise.
5. Click Search.
6. Select the line for Docs@Work for Android enterprise.
Do not select the Docs@Work for Android enterprise preview app.
7. Click Next.
8. Select “5.0” for Min. OS Version.
9. Click Next.
10. Select Install this app for Android enterprise.
You may need to scroll down to see the option. Additional fields are then displayed.
11. Use the following table to set up the Configurations section:

Item Description

Silently Install Select to automatically install the app when the device checks in.

Auto Update this App Select to automatically update the app when a new version is available.

Docs@Work 2.0.0 for Android enterprise (Android for Work) | 3

Item Description

Configurations

CSS URL If you are using MobileIron Content Security Service to manage Docs@Work,
enter the URL for the Content Security Service.
Otherwise, ignore this field.

EMM Server URL Enter the URL for the MobileIron Core on which you are creating this
configuration.

Device UUID Enter $DEVICE_UUID$

User ID Enter $USERID$

Group Sites Enter content site configuration in JSON format.

See “Generating Group and Published site configuration” on page 7 to
generate and copy and paste the configuration.
Example:
[{"name":"averailserver02","url":"https://
averailserver02.corp.averail.com","domain":"SharePoint","subDomain":"Corpo
rate","webView":"false","priority":"false"}, {"name":"webdav06 ", "url": "http://
averailserver06.corp.averail.com","domain":"WebDAV",
"subDomain":"CloudStorage"}]
Not applicable for Content Security Service mode.

Published Sites Config Enter content site configuration in JSON format:

See “Generating Group and Published site configuration” on page 7 to
generate and copy and paste the configuration.
Example:
{"interval";180, "wifi";true, "skipFiles"; 500,"maxDocs";50}
Not applicable for Content Security Service mode.

Log Level Select one of the following options to specify the level of detail for logs:
• DEBUG: Includes debug level information for application flow and to
request response messages for target repositories. This is the highest level
and verbose, so choose this level only when needed.
• INFO: Includes only information related to specific flows and requests.
• WARNING: Includes only warnings about runtime errors and target
repositories.
• ERROR: Includes only runtime errors, and error and status codes from
requests to target repositories.
Not applicable for Content Security Service mode.

Support Email Id Enter a valid email address.

The email address is automatically populated when the device user emails the
device logs.

Docs@Work 2.0.0 for Android enterprise (Android for Work) | 4

Item Description

Blocked Storage Domains Enter one or more of the following to block device users from adding the
content site to Docs@Work:
• Box
• Dropbox
• Microsoft SharePoint
• WebDAV
Enter the values as a semicolon (;) separated list.
Example: Box;Dropbox
Microsoft SharePoint includes Office 365 SharePoint sites.
Not applicable for Content Security Service mode.
User Sites Restrictions Enter the site type and number in the following format to restrict the number of
User sites that a device user can add:

Site type1:number; Site type2:number.

Valid entries for site type are: SharePoint, Box, Dropbox, WebDAV.
Number is a positive integer greater than 0.
Example: SharePoint:2; Box:1
In this example, the device user will be able to add up to two SharePoint sites,
and only one Box site. There are no restrictions on any other type site.
If a site type is not configured, there are no restrictions on the number of User
sites for that site type.
Restricting number of User sites has no impact on blocked sites. This
configuration is ignored if Disable User Sites is true.
Not applicable for Content Security Service mode.
Disable User Sites Enter true to prevent device users from adding sites to Docs@Work.
Not applicable for Content Security Service mode.

Docs@Work 2.0.0 for Android enterprise (Android for Work) | 5

 Item Description

Disable Editing Enter true to disable editing of documents in Docs@Work.

Disables the following in My Files and all content sites in Docs@Work:
• Editing.
• Creating new files and folders.
• Importing images from photo gallery.
• Uploading to and deleting files in the backend resource.

Auto-fill Credentials Config Enter parameters for the content site in the following JSON format:
{"URL":{"domainType": "DomainType","userName":"$USERID$"},
"default":“Domain/$USERID$”}
Note the following for JSON format:
- Ensure that there are no spaces.
- Values are case sensitive.
- Ensure that the JSON format is valid.
- The variable for user name can be preceded by either a single forward
slash or two back slashes: Domain/$USERID$ or Domain\\$USERID$
Tips
- Copying and pasting JSON strings may result in invalid JSON.
- Validate the JSON string. There are many sites, example: jsonlint.com,
that will validate the JSON string.
Description:
URL: Enter the URL for the content site. Include the protocol. Example: http,
https.
Domain Type: Enter one of the following: SharePoint, WebDAV, Box,
BoxEnterprise, GoogleDrive.
Domain: Enter the domain name to which the username defaults if the
username for the URL cannot be resolved. Variables are not supported.
Examples:
• {"https://sharepoint.miacme.com":
{"domainType":"SharePoint","userName":"miacme/
$USERID$"},"default":“miacme.com/$USERID$”}
• {"https://
sharepoint.miacme.com":{"domainType":"SharePoint","userName":"miacm
e\\$USERID$"},"default":"miacme.com\\$USERID$"}
• {"default": "domain/$USERID$"}

12. Click Finish.

13. Apply the Docs@Work for Android enterprise app to the appropriate labels to distribute the app to Android
enterprise devices.

Docs@Work 2.0.0 for Android enterprise (Android for Work) | 6

Generating Group and Published site configuration
MobileIron recommends generating a valid JSON with the Configuration Tool. This ensures that a valid JSON is
configured in the Docs@Work for Android enterprise app configuration.

To generate valid JSON configuration for a content site:

1. Complete the Docs@Work for Android enterprise configuration without Group Site and Published Site
configuration and apply to an Android enterprise device.
2. In Docs@Work for Android enterprise, go to Settings > Configuration Tool.
3. Click on the “+” icon to configure a content site.
4. Configure the Site Name, URL, including type of site (Sharepoint or WebDAV), Sub domain, Authentication,
Published Site, and Web View.
5. Add additional sites as needed.
6. Click on the upload icon at top of the screen to export the file.
7. Email the file to an email account from where it can be copied and pasted into the Groups Sites and
Published Site Config fields.

Add attachments from Docs@Work in an Email

Docs@Work is now available to add attachments when you compose an email from Email+ or any other email
clients. The number and size of files that you attach to an email is at the discretion of the email client. For example,
AppConnect.

Android enterprise Email+ allows multiple file attachments. You can select multiple files to add as attachments.

Docs@Work 2.0.0 for Android enterprise (Android for Work) | 7

What users see
The Docs@Work app for Android behaves similarly to the Docs@Work app for Android enterprise. For
information on how to use the Docs@Work app, see the “What the user sees” chapter in the MobileIron
Docs@Work for Android Guide.

Docs@Work 2.0.0 for Android enterprise (Android for Work) | 8

Copyright © 2014 - 2017 MobileIron, Inc. All Rights Reserved.

Any reproduction or redistribution of part or all of these materials is strictly prohibited. Information in this
publication is subject to change without notice. MobileIron, Inc. does not warrant the use of this publication. For
some phone images, a third-party database and image library, Copyright © 2007-2009 Aeleeta's Art and Design
Studio, is used. This database and image library cannot be distributed separate from the MobileIron product.

“MobileIron,” the MobileIron logos and other trade names, trademarks or service marks of MobileIron, Inc.
appearing in this documentation are the property of MobileIron, Inc. This documentation contains additional trade
names, trademarks and service marks of others, which are the property of their respective owners. We do not
intend our use or display of other companies’ trade names, trademarks or service marks to imply a relationship
with, or endorsement or sponsorship of us by, these other companies.