iManage Work Mobility for iOS
iManage Work Mobility for iOS supports MAC in two ways:
You can use iManage Control Center to create an .immconfig file and load it into our MDM tool.
If a file upload is not supported on your MDM tool, you can manually enter the key-value pairs.
For more information on configuration files deployment, see the Deploying configuration files chapter in iManage Work Mobility Documentation of Help Center.
The following table lists the key-value pairs that can be specified:
Table: Key-value Pairs
Identifier |
Type |
Default |
Description |
version |
Integer |
2 |
Specifies the format version for configuration and is required. It must be set to 2. |
POLICY CONFIGURATION |
|||
open_in_receive |
Boolean |
true |
Use this policy to restrict users from receiving document(s) in iManage Work Mobility for iOS from other applications. Set one of the following parameters: true - users can import documents to iManage Work Mobility for iOS from other applications. false - restricts the users from importing documents to the iManage Work Mobility for iOS from other applications. |
open_in_send |
Boolean |
true |
Use this policy to restrict users from sending document(s) in iManage Work Mobility for iOS to other applications. Set one of the following parameters: true - enables the users to send documents from iManage Work Mobility for iOS to other applications through Open In feature of iOS. false - documents cannot be sent from iManage Work Mobility for iOS to other applications. |
enable_native_email |
Boolean |
true |
Use this policy to restrict users from sending document(s) as email attachment from iManage Work Mobility for iOS through native email (Mail app) application. Set one of the following parameters: true - enables the users to send the iManage Work document(s) as email attachments using the iOS Mail app. false - prevents the users from sending iManage Work document(s) as email attachments. |
enable_app_extensions |
Boolean |
true |
Use this policy to invoke Storage Provider Extension (SPE), which allows native application to access documents from iManage Work Mobility for iOS on users device, in a safe and convenient way . Set one of the following parameters: true - enables the SPE. false - the SPE is disabled. |
enable_airdrop |
Boolean |
true |
Use this policy to restrict users from sharing document in iManage Work Mobility for iOS using AirDrop. Apple's AirDrop feature enables the transfer of files among supported macOS computers and iOS devices without using mail or a mass storage device. Set one of the following parameters: true - enables the user to share the downloaded documents through AirDrop. false - disables sharing the documents through AirDrop. |
enable_printing |
Boolean |
true |
Use this policy to restrict users from printing documents from iManage Work Mobility for iOS. Set one of the following parameters: true - enables the users to print downloaded documents through iOS AirPrint. false - disables the printing of documents. |
enable_downloading |
Boolean |
true |
Use this policy to restrict users from downloading documents to their mobile devices from iManage Work Mobility for iOS. Set one of the following parameters: true - documents may be downloaded to the device. false - prevents bulk download of documents to the device. |
enable_privacy_curtain |
Boolean |
true |
Use this policy to disable Privacy Curtain. Privacy Curtain is a security feature that obscures the contents of iManage Work Mobility for iOS when the application is not active. Set one of the following parameters for the Privacy Curtain: true - the Privacy Curtain is displayed when the application is not active, obscuring any content that is on the screen. false - the Privacy Curtain is disabled. |
enable_touch_id_for_passcode |
Boolean |
true |
Use this policy to prevent users from signing into iManage Work Mobility for iOS through Touch ID on their mobile device. Touch ID is Apple's fingerprint identity sensor and is a form of bio-metric security meant to be more convenient than entering a passcode or password, especially on iPhones, iPads, and Macs. Set one of the following parameters: true - the user gets an option to enable Touch ID when configuring App Lock. false - Touch ID is not offered. |
show_demo_connection |
Boolean |
true |
Server connection that connects to a public iManage demo server, which can be used to test the iManage Work Mobility for iOS application before it is deployed in your environment. Set one of the following parameters: true - the Demo connection is displayed at the bottom of the servers list on the sign in screen. false - the Demo connection is not displayed. |
number_of_passcode_retries_min_3_max_20_default_10 |
Integer |
10 |
This is the number of times the application passcode can be entered before all locally stored data is erased from the device (no data is impacted on the server). The minimum value is 3, and the maximum is 20. |
passcode_grace_period_seconds_min_10_max_999999999_default_60 |
Integer |
10 |
When switching away from the application, there is a time delay before the App Lock is enforced, requiring the user to enter the application passcode (or if configured, Touch ID). The minimum is 10 seconds; the maximum is 999999999 seconds (effectively only requiring the user to enter the application passcode or use Touch ID when the application starts or restarts). |
prevent_copy_to_clipboard |
Boolean |
false |
Use this policy to restrict users from copying content in iManage Work Mobility for iOS, and pasting it into clipboard or pasteboard. This policy configuration secures iManage Work data.
Set one of the following parameters:
false -
is the default setting, and allows users to copy text from an iManage document to other applications. true - the clipboard or pasteboard in iManage Work Mobility for iOS is cleared when a user copies text from any document. This effectively stops copying any data from iManage Work Mobility for iOS as the user cannot paste any text into other application(s).
|
SERVER CONFIGURATION Any number of servers may be included. These are displayed in numerical order based on the integer in the identifier, starting with 0. For example, server2_uuid is the third server. |
|||
server0_uuid |
String |
- |
A UUID to uniquely identify this entry. These can be generated here. Example: b985dc4b-3232-4719-9d1d-cf0162badc30 |
server0_name |
String |
- |
The name that is displayed in the application. Example: Chicago |
server0_auth |
Integer |
- |
The authentication type for the server. The valid values are: 0 - Explicit/Network 1 - ADFS (On premises ADFS Server) 2 - Common login For more information on how the users are authenticated, see User authentication process. |
server0_url |
Text |
- |
The Work Server name that was used during the installation. Please be sure to type the value as a fully qualified domain name that matches the SSL certification. For example, boston_office.abjualaw.com |
User authentication process
Standard login supports both Work credentials and domain/username & password for explicit network authentication. The credentials are stored in an iCloud Keychain.
TIP:
For more information on the iCloud Keychain, go to https://support.apple.com/en-us/HT204085.
A cookie is stored on the device, but it is not shared with other applications or browsers. When the access token expires, it is renewed without displaying the credentials screen. This ensures that the users are not prompted to sign in on the login screen.
However, the login screen is displayed only when:
a user provides invalid credentials (user name or password).
the user credentials have changed on the server.
For example, if your company policy requires the user to change the password after a certain period.
ADFS authentication displays an embedded web view where the user must follow whatever authentication procedures the company has defined for the ADFS implementation.