Main steps for configuring Docs@Work for iOS (Ivanti Neurons for MDM)

Configuration for Docs@Work is done in Ivanti Neurons for MDM. Following are the main steps for configuring Docs@Work for iOS on Ivanti Neurons for MDM:

1. Adding Docs@Work for iOS on Ivanti Neurons for MDM
2. Configuring Docs@Work for iOS on Ivanti Neurons for MDM
3. (Optional) Configuring AppTunnel for Docs@Work

Adding Docs@Work for iOS on Ivanti Neurons for MDM

Docs@Work for iOS is available in the app catalog in Ivanti Neurons for MDM.

Procedure 

1. In Ivanti Neurons for MDM, go to Apps > App Catalog > +Add.
2. In Business Apps, click Docs@Work (iOS).
3. Make any updates as necessary and click Next. You can change the category and add a description.
4. Choose a distribution option for the app and click Next.
5. Update the default install settings or add install settings as necessary.
6. Update the promotion settings or add promotion settings as necessary.
7. For Docs@Work configuration, click + icon to add Docs@Work configuration.

Next steps 

Configuring Docs@Work for iOS on Ivanti Neurons for MDM

Configuring Docs@Work for iOS on Ivanti Neurons for MDM

After adding Docs@Work to Ivanti Neurons for MDM, configure Docs@Work on Ivanti Neurons for MDM.

Procedure 

1. In the Docs@Work configuration, enter a name for the configuration.
2. Configure the Docs@Work settings as needed.
3. Add any custom configurations for the app in AppConnect Custom Configuration.
4. Add any certificates that are required.
5. Choose a distribution option for the configuration and click Done.
6. The configuration is distributed to the subset of the devices to which the app is distributed

Content sites configured in the Doc@Work configuration are automatically added to the Docs@Work app. Device user action is not required.

Related topics 

• See Docs@Work configuration field description (Ivanti EPMM and Ivanti Neurons for MDM) for description of the fields.

(Optional) Configuring AppTunnel for Docs@Work

You create an AppTunnel service in Standalone Sentry as part of the AppTunnel setup required to tunnel traffic to content repositories. CIFS traffic must be tunneled through Standalone Sentry.

Before you begin 

Ensure that you have a Standalone Sentry that is set up for AppTunnel and the necessary device authentication is also configured. See “Configuring Standalone Sentry for app tunneling” in the Sentry Guide.

Procedure 

1. In the Docs@Work App Configuration > AppTunnel, click + icon.
2. Enter a name for the configuration.
3. Optionally add a description for this configuration.
4. Enter the domain wildcards for the App Tunnel.
5. Choose a distribution level for this Configuration.

Related topics 

For more information on configuring AppTunnel, advanced traffic control, and AppTunnel rules, see “Configuring an AppTunnel service” in the AppConnect and AppTunnel Guide.

Default iOS AppConnect Configuration

The Default iOS AppConnect Configuration is enabled by default and applied to all iOS devices. The iOS AppConnect Configuration specifies AppConnect app settings such as AppConnect passcode and data loss prevention requirements.

You may edit the Default iOS AppConnect Configuration (Configurations > Default iOS AppConnect Configuration) if needed. The changes will be applied to all iOS devices. If you want the setting to be applied to only some iOS devices, create a new AppConnect Device configuration (Configurations > AppConnect Device) for iOS and distribute the new configuration to a subset of iOS devices.

User-added sites

Users can add the following types of sites:

• Box
• Cloud Storage
• Dropbox
• Network Drive
• SharePoint

To add corporate sites, the user will need the following information:

• The site’s URL. The URL must include http:// or https://. Both domain name and IP address are supported.
• Type of Authentication for Network drives. The authentication setting is labeled No Authentication.
• Device users should enable this setting, if the site does not require authentication.
• Type of authentication for SharePoint servers:

Authentication type	Description
Corporate	User authenticates with on-premise SharePoint using either Windows NTLM or Forms-based authentication with corporate credentials. User credentials can be domain\username or just username, depending on how SharePoint is set up with Windows domain authentication.
Office 365	User authenticates with Office 365 SharePoint using the authentication mechanism supported by Office 365. User credentials map to the user’s account on Office 365, or to the user’s AD credentials. If Office 365 has been integrated with corporate AD, then user’s SharePoint credentials map to AD credentials.
NoAuthn	User doesn’t need to provide credentials for authentication. The SharePoint server supports anonymous access..

• Web View: For SharePoint sites, the user can turn on Web View to be able to view and navigate SharePoint folders in browser view.

Related topics 

For more information about topics such as app delegation, see the Ivanti Neurons for MDM Administrator Guide.