Main steps for configuring Docs@Work for Android AppConnect (Cloud)

Following are the main steps for configuring and deploying Docs@Work for Android AppConnect on Cloud:

Adding Docs@Work for Android AppConnect to Cloud

You add Docs@Work in the same manner you would add any other Android in-house app. After adding to Cloud, you can distribute the app to devices.


1. In the Cloud, go to Apps > App Catalog > +Add > In-House. Add the app just as you would any in-house app.
2. After adding the apps, select the distribution option that includes the users and devices to which you want to make Docs@Work for Android available.
3. Click Next. If the app was already in the catalog and you are editing the app, click Save.

Next steps 

Configuring Docs@Work for Android AppConnect in Cloud

For details on adding in-house apps for Android, see the Cloud Administrator Guide or click on Help in Cloud.

Configuring Docs@Work for Android AppConnect in Cloud

Before you begin 

Decide which repositories you want to make available. All repositories you configure for Docs@Work are visible to all users. You can provide select users with instructions for accessing restricted repositories.

Decide whether you want to make each repository a published site. Content on published sites is automatically downloaded and mirrored on devices.

Collect the following information for each repository:

URL for the site

type of repository (SharePoint, WebDAV)

subtype of repository (Office 365, NetworkDrive, and so on.)

To configure Docs@Work on Cloud follow these steps:


1. Edit the Default AppConnect device configuration or create a new one.

If the same settings will apply to all user groups and all AppConnect-enabled apps, then you can edit the default configuration. Only one AppConnect device configuration can be applied to a given device and all AppConnect-enabled apps on that device.

2. Add the Docs@Work app to the app catalog.

Under Advanced Options and App Configuration, provide the following information for each content site you want to display in Docs@Work:




Content Sites


Enter a URL for the content site.

The URL must include http:// or https://. Both domain name and IP address are supported.


Select the type of content site you are configuring:

SharePoint (Select SharePoint for One Drive for Business.)



Select the subdomain type for the content site:

SharePoint: Office 365, Corporate

Select Office 365 if you are configuring OneDrive for Business.

WebDAV: NetworkDrive, CloudStorage



Select if you want the device to authenticate to the server.

Published Site

Select to designate the site as a published site.

All content in a published site is automatically downloaded and mirrored locally on the device when the device syncs. If the option is not selected, the user must manually download the content.

A Web View site cannot be configured as a published site, and a published site cannot be configured as a Web View site.

Published sites for SharePoint are not supported at root, site, and subsite levels. Published sites are supported at document library and folder levels. Ivanti recommends that published sites be set for publishing 50-100 documents.

Web View

Only for SharePoint domains.

Select to allow users to view and navigate SharePoint folders in browser view.

Provide the following information for the published sites:



Published site

Update Mode

Specify the method devices can use to update published sites. Select either Wi-Fi Only or Wi-Fi and Cellular. Ivanti recommends using Wi-Fi Only if you support large number of documents.

Update Interval (Minutes)

Specify the updated interval for published sites.

The Default setting is every 60 minutes.

Max auto download size (MB)

Specify the maximum file size for automatic download. Files above this size will not be automatically downloaded. The default setting is 500 MB.

Max documents per update

Specify the maximum number of documents to update for each updated site. Only the number of files specified will be updated. The default setting is 100 files.

Select a device group for app distribution.

3. Add the Key and value for AppConnect Custom Configuration, for example: watermark_text key-value pair.
4. Add the Key and value for AppConnect Certificate Configuration, for example: signing_certificate_ca_n key-value pair.