iManage
Overview for configuring iManage to connect to CAM
CAM integrates with the iManage Work Cloud, Cloud iManage, and iManage on-premises environments.
Note: The procedure for configuring iManage Work Cloud/Cloud iManage and iManage on-premises is almost the same. You can still utilize the provide screenshots and steps for both.
Warning: The user, and not Litera, is responsible for creating the enterprise proxy application (because CAM/Litera is not the one deciding where their proxy connector is to be placed) AND then proceeding with the app registration steps.
Two apps are to be setup:
The enterprise proxy application
The app registration for CAM
To integrate CAM with the iManage Work Cloud, the iManage cloud servers must be configured using the below steps.
To connect an on-premises iManage environment, the iManage server needs to be accessible from the internet. This can be done as follows:
Expose the iManage Server via a static-ip/firewall. Click here for information on whitelisting CAM’s IP.
Use Azure Proxy.
Add trusted-ip restriction as an additional security measure.
You can add and manage multiple iManage servers, define the workspaces' naming convention, the template rules to be applied, and the default folder metadata.
Warning: The Client ID & the Client Secret ID must be updated in the iManage Control Center (IMCC) to support API Authentication and enable CAM to integrate with the iManage Server. Read here for detailed instructions to update the Client ID & Secret ID.
- 1 Configuring NRTAdmin Access
- 2 iManage Configuration
- 3 Pre-reqs
- 4 Updating Prosperoware-CAM Basic Package To Resolve Connectivity Issues
- 5 iManage Server Configuration
- 5.1 Fields
- 5.2 Mapping Metadata
- 5.3 Workspace Name Rules and Format
- 5.4 Template Rules
- 5.5 Folder Metadata
- 5.6 Group Rule
- 5.7 Document Metadata
- 5.8 Workspace Edit Name Rule
- 5.9 Azure Proxy Server app
- 5.10 Delegated Permissions on Microsoft Graph
- 5.10.1 Redirect Endpoint URI's
- 5.11 iManage Token Expiry Extension
Configuring NRTAdmin Access
For iManage, create an NRTAdmin account role in iManage that does not have the View Document permission granted to the role. Assign this to the CAM iManage account. That allows CAM to read all metadata but cannot download or view the document or its content.
The NRTAdmin role assigned to the account must be granted permission to access iManage Control Center.
The NRT Admin account is necessary for the CAM connection to iManage in many modules!
This is so we can:
Provision workspaces: the ability to create, modify, secure, and delete workspaces.
Work with Metadata: the ability to create, modify and delete metadata
Manage Users/Groups: the ability to create, modify, disable & manage group memberships
Signs of a missing NRTAdmin acct or no Control Center access:
CAM can’t access iManage Control Center with the account.
Generate Template doesn’t return results.
iManage Configuration
CAM iManage Control Center (IMCC)
Tip: First, whitelist the CAM IP's listed in the following table on iManage before uploading the zip into IMCC.
Pre-reqs
Whitelist URLs
Ensure the iManage connection is a “Virtual” account type.
Whitelist URLs
Whitelist if your tenant is hosted in any of the following zones:
Zone | Whitelist the IP | Whitelist the IP |
---|
Zone | Whitelist the IP | Whitelist the IP |
---|---|---|
US(prosperoware.io) | 18.205.167.41 | 34.198.68.230 |
18.130.49.85 | 3.9.236.119 | |
EU(prosperoware.eu) | 52.214.142.149 | 54.76.178.8 |
Us West(Oregon)(camuswest.com) | 44.234.16.65 | 52.38.245.112 |
Apac(Singapore)(camapac.com) | 3.0.77.244 | 52.76.160.89 |
Australia (Sydney)(pwcamau.com) | 13.55.127.223 | 3.105.163.118 |
Canada(Central)(pwcamcanada.com) | 3.96.104.12 | 3.96.240.119 |
For iManage Work Cloud or On Premise
Download the iManage Authentication and Web Extension
Navigate to Administration > Downloads and download the iManage Web Extension package. This package includes the iManage Authentication Manifest file and CAM Commands web extension. If once downloaded, you wish to edit the CAM Command web extensions, please skip to 2a.
If you do not want to use/upload the CAM Commands web extension, click on Basic CAM IMCC package without the web extensions for the Authentication Manifest file only. (Basic package updated 4/15/2025)
Upload iManage Authentication (and Web Extensions if applicable)
For steps on editing CAM Commands and extensions, visit: CAM Commands | Deploying Web Extensions .
Add the redirect urls as directed in IMCC under Authentication, use the table: iManage | Redirect Endpoint URI
In the iManage Control Center, in the left-hand side panel under Configure, select System Setup>Applications.
In the Applications page, click the + sign on the top-right side of the page.
Click Upload Package and upload the downloaded file.
The details from the file are auto-populated on the Configuration and Authentication page. Do not
edit the auto-populated information. Click Continue.Update the Security details.
Click Finish.
For http://cloudimanage.com configurations:
For steps on editing CAM Commands and extensions, visit: CAM Commands | Deploying Web Extensions .
Add the redirect urls as directed in IMCC under Authentication, use the table: iManage | Redirect Endpoint URI
Please set the refresh token in iMCC as Yes. If the refresh token is set to No in iMCC, the External configuration may show as Red and error.
In the iManage Control Center, in the left-hand side panel under Configure, select System Setup>Applications.
In the Applications page, click the + sign on the top right-hand corner of the page.
Search for Prosperoware – CAM and follow the instructions until completion.
Editing the web extensions (iManage Work or On-Premise)
For steps on configuring CAM Commands and extensions, visit CAM Commands | Deploying Web Extensions .
Add the redirect urls as directed in IMCC under Authentication, use the table: iManage | Redirect Endpoint URI
If the web extensions package is to be used, the extension files should be updated to your system.
Extract and open up the CAM_IMCC_web_extensions.zip file.
Go into the web_extensions folder.
There should be six files:
AspNetManageFolderMenuItem.yaml ---- This allows the user to Manage Folders and create on-demand folders from CAM.
AspNetDeleteFolderMenuItem.yaml ---- This allows to delete not-required and empty folders from iManage Web and DeskSite.
AspNetCreateWorkspaceMenuItem.yaml ---- This allows the Workspace Wizard (Request Workflow) to appear in Work 10.
AspNetEditNameAndProfileMenuItem.yaml ---- This allows the end user to Update Workspace, Folder name, or Profile from the iManage system. Based on the criteria set in CAM:
in External system configuration for workspace and/or
in Template editor for the folder and/or
in Layout for Profile.
AspNetShareFolderMenuItem.yaml --- This allows end users to share a folder if a user has access to the workspace (read/write or above) and also has CAM permission to share.
AspNetShareDocumentMenuItem.yaml --- This allows end users to share a document if a user has access to the workspace (read/write or above) and also has CAM permission to share.
Note: User can enter the default value as follows:
Domain name i.e tenant name to which you want to connect web commands. E.g "http://clienttenant.prosperoware.io".
Application id ("CAM_TEAM_APP_ID" : "2fb4fc8a-fd7a-4fb0-9ff7-dedf63555ba2") to connect with CAM Teams App. After installation CAM into the MS Team app, login into the CAM Team app.
For steps on config get the wizard ID from CAM
Login to the CAM tenant.
In your browser (preferably Chrome or Firefox), Inspect the page (CTRL+SHIFT+I).
In the Chrome/Firefox inspection panel, click on the Network tab if not selected.
Click on the Plus icon in CAM to get to a workspace wizard
In the inspection panel, in the 'Name' Column, an entry called 'workspacewizard' appears toward the bottom of the list.
Click on the first 'workspacewizard' entry.
Inside the Network Tab, click on the Response Tab.
In Chrome scroll right until you see "wizardId". In Firefox, wizardId will display right on the screen.
The number following, such as " 2b04aeff4cb52638a3c46420668faa0d " is the Wizard ID.
Add the wizardid into the URL like such: https://tenantname.prosperoware.io/workspacewizard?wizardId=2b04aeff4cb52638a3c46420668faa0d.
Zip the files backup after making the changes.
Updating Prosperoware-CAM Basic Package To Resolve Connectivity Issues
If you are experiencing connectivity issue with your CAM iManage connections, please update "Prosperoware - CAM" application package in iManage Control Center (iMCC).
Updating iManage Work or Mobility
Download the new package from Basic CAM IMCC package without the web extensions. (Basic package updated 4/15/2025)
Log in to the iManage Control Center (iMCC):
Navigate to Applications.
Locate the Prosperoware-CAM Application within the list.
Open the Prosperoware-CAM Application. If on the cloud, please select Update Package on the upper right and follow the below steps.
Scroll to the Authentication Section.
Verify what the current Client Secret value is. If it differs from the new secret on the Basic IMCC package, edit it to the new secret by following Steps 8-15.
Click on the Edit option beside the Authentication section.
Replace the existing Client Secret with the new value.
Save the Settings.
Making this change may "disable" this application in iManage. Once you save the settings, please enable to the application from IMCC and proceed with below steps.
Log in to CAM.
Navigate to Administration > External System Configuration > iManage.
Edit the Repository and Validate the connection to ensure the new Client Secret is working correctly.
Once the validation is successful, select Update to save the new settings.
Updating iManage Cloud
Log in to the iManage Control Center (iMCC)
Navigate to Applications.
Locate the "Prosperoware - CAM" Application within the list and open it.
From the top menu, select "Update Package" and follow the wizard to finish the update process.
Log in to CAM.
Navigate to Administration > External System Configuration > iManage.
Edit the Repository and Validate the connection to ensure the new Client Secret is working correctly.
Once the validation is successful, select Update to save the new settings.
iManage Server Configuration
Go to Administration > External System Configuration > Settings and ensure that the iManage integration is active and click Save.
Click the iManage tab.
In the panel for iManage Server click the Add New button.
In the window for iManage Server Setup- Add New, type information in the provided fields, based on the table below.
Click Save. You can add multiple iManage Servers.
Fields
Field | Description |
---|
Field | Description |
---|---|
Is Azure Proxy Used? | Select Yes to set this server to access using Azure Proxy server iManage | Azure Proxy |
Is version 10.3 or above? | If the user selects Yes, then the “User id and Password“ field will hide and authentication will be done through a common authentication dialog. Litera recommends that the account be virtual if using Azure Proxy, which is the option in iManage configuration is Is 10.3= No Note: Users need to register CAM app in the Controls Center for an access support OAuth 10.3 or above. Enter the Redirect URLs accordingly to your region from the list given in @ section Azure Proxy Server app to access on behalf of CAM >Redirect Endpoint URI's |
Server Name | Enter a name for the server. This is a required field. (e.g. iManageProd). Note: Spaces or .,*? are not allowed in the name. |
URL | The address of the server. This is a required field. The URL should be like https://servername-mobility.imanage.work for cloud systems Changes to URL’s/ DomainsIf URL’s or domains/subdomains need to be changed, make the edits here and click re-validate, and save. If this is due to a cloud migration, or link workspaces are affected, please read the following guide: Migration to Cloud iManage |
Client Id | With the new iManage dynamic credentials, clients can input the client id and secret fields. If you haven’t done this before, please input these and click save. |
Client Secret | With the new iManage dynamic credentials, clients can input the client id and secret fields. If you haven’t done this before, please input these and click save. |
Azure ProxyIf Is Azure Proxy Used? is set to Yes, then the below 4 fields are displayed. Read here for detailed instructions to retrieve these fields. Litera recommends that the account be virtual if using Azure Proxy, set the option in this iManage configuration to Is 10.3= No You are responsible of creating the enterprise proxy application (because CAM/Litera is not the one deciding where their proxy connector be placed). | |
Application Id | Enter the Application (client) ID from the Azure Active DirectoryPortal. |
Application Password | Enter the application password. |
Directory (Tenant) Id | Enter the Directory Id from the Azure Active Directory. |
Get Token button | It will be enabled once URL, Application Id, Application Password and Directory (Tenant) Id is entered. Click the Get Token button, and enter the log in details. On successful login, the token is generated. |
User Id | Enter the user name to access the server. This is a required field. |
Password | Enter the password to access the server. This is a required field. |
Validation | Click the Validate button to verify the the login credentials for the server. |
Token | On a successful validation a token is auto-generated and displayed here. If the validation is unsuccessful, a Validation Failed message is displayed. When updating an expired token, the popup will display the up to date redirect url for confirmation. |
Is Default | Select Yes to set this server as the default repository. If the repository name is not specified in the uploaded CSV file, the data will be updated to the default repository. |
Dynamic Group | Select Yes to create a dynamic group in the iManage workspace. Selecting this option will allow for multiple users to be added to the dynamic group. Read Dynamic Groups for more details to create and add users to the group. Note: The dynamic group creation option specified in the CSV file will override the option set here. |
Default Database | Select the default database for iManage. The options available for selection here are the database pre-configured in the iManage. |
Default Security | Set the default security for the workspace.
Notes:
|
Default Password | The default password set here needs to match iManage’s password requirements:
Tip: It is recommended that all iManage connections (on-premises, private cloud, and cloudimanage.com) follow the same rules if filling out the default password section. |
Server Alias | Use for CAM commands. Set to CloudiManage.com. If you get the warning This error is due to a missing configuration in CAM, it means the server alias might be wrong. This should match with the iManage URL. |
Permission Mapping | Set permission based on CAM Roles. Common CAM roles are following:
Save the server information. The permissions for these roles can only be edited after the server information has been saved. If the server details have not been saved, the Edit button will be grayed out. If hovered over, a tooltip will warn users about this. |
Click on each type of Security Role to update their respective permissions. | |
Read | This allows access to only view documents, properties/metadata, etc. |
Read Write | This allows full access to the document (view and edit), but limited control on properties/metadata and no ability to change security (including for the folder, workspace, etc.) |
Full Access | This allows full access to the document (view/edit/share) and full control over properties/metadata and also the security (including for the folder, workspace, etc.) |
Actions |
|
Add multiple tokens in the server configuration for iManage
Adding additional Client Tokens for different credentials or tokens to the client is possible. This feature is applicable to those tenants who have their own client stack. It will be used for Data Sync and ETL/Data Uploader processes.
To configure a recently added iManage server or edit/update the existing servers' details with new Token, follow the below steps:
Select the System you want to edit/update as shown in the following screenshot.
Click on the Edit option.
Click on Add Client Token. The Server setup -Edit dialogue box appears.
Click on Add Client Token. The Add Client Token dialogue box opens.
Enter the following details.
Fields | Description |
Name | Enter a unique name. By default, it displays “Client Token”. User can change to a new unique name. |
Provider | Displays default provider as Client. |
User Id | Enter the username to access the server. This is a required field. |
Password | Enter the password to access the server. This is a required field. |
Validation | Click the Validate button to verify the login credentials for the server. |
Token | On a successful validation a token is auto-generated and displayed. If the validation is unsuccessful, a Validation Failed message is displayed. |
Click Add to add new token or click Cancel to cancel the dialogue
Note: A permission similar to No Access can also be applied when adding users/groups to a workspace/folder with permission as Deny. The workspace/folder will not be visible to the users/groups. For e.g. Permission updated as: alexey.marcus@prosperoware.com|false#23/12/2019*Admin$false
The list of information is displayed in the following columns:
Column Name | Description |
---|
Column Name | Description |
---|---|
Repository | The server name entered above. Click on the link to open the iManage login page. Hover your cursor over the name to view the server URL. |
Credentials | Will display Configured, if the user name and password are successfully validated during configuration. |
Last Modified | The last updated date and time |
Last Modified By | Name of the user who was logged in when the change was made |
Status | The health status of configured system |
Is Default | Is updated based on selection made during configuration. |
Dynamic Group | Is updated based on selection made during configuration. |
Server | Click Edit to edit the configuration set up. The iManage Server Setup- Edit window is displayed. Make the necessary changes and click Update. Click Delete to remove the server setup. |
Metadata | Click Manage to map the Metadata to the repository. The Metadata Mapping window is displayed. |
Caution: By design, after successfully adding a client token, the userid and password details associated with that user will show empty if a user tries to edit that client token.
Mapping Metadata
Best Practice- Don’t use invalid characters in the metadata creation or mapping.
In the Metadata Mapping window, the columns are updated with the metadata auto-mapped from CAM to iManage. If the columns are not populated, click the Auto Discover button to automatically find and map the metadata from CAM to iManage. The default database displayed in the Select Database drop-down is based on the database selected in the iManage server configuration.
A matrix of default iManage to CAM Metadata Mapping is found here iManage to CAM Metadata Mapping, or in the Litera Customer Center.
How to Map metadata documentation from a general perspective is located: Metadata
To manually add and map additional metadata:
Click the Add Metadata button.
In the Add Metadata Mapping window type information in the provided fields, based on the table below,
Column Name | Description |
---|
Column Name | Description |
---|---|
CAM | Select the metadata from CAM to be mapped to iManage. To assign a metadata, either click the drop-down menu and select from the list or manually enter the value, which will auto-complete if it is assigned in Administration>Metadata. |
iManage | Select the metadata from iManage to map to CAM. The drop-down will include all the metadata defined in the iManage database. |
Is Unique Identifier | Select Yes to set the metadata value as a unique identifier. When a job is uploaded with a unique metadata, CAM will only modify the iManage workspace(s) that have the unique metadata assigned. If the unique metadata does exist in any of the existing workspace(s), CAM will create a new workspace for the uploaded job. |
Click Save.
Tip: You can also copy metadata mapping from one database to another. Use the CopyFrom parameter in a CSV job to copy the metadata mappings from one DB to the other. All the metadata mapping will be copied from the source database to the target database.
The list of information is displayed in the following columns:
Column Name | Description |
---|
Column Name | Description |
---|---|
CAM | List of the metadata from CAM mapped to iManage. |
iManage | List of the metadata from iManage mapped to CAM |
Unique Identifier | Is updated based on selection made when adding metadata |
Action | Click to edit the mapped metadata. The Edit Metadata Mapping window is displayed. Make the necessary changes and click Update. Click Delete to delete the metadata mapping. |
Note: • CAM supports all special characters that iManage supports for metadata values !@#$%^&*()+[]{};"|:<>/<>/.
Workspace Name Rules and Format
To define the iManage workspace names rules and format to be applied:
Click the iManage tab.
In the panel for Workspace Name Rules and Format click the Add New button.
In the window for Rule Creator, type information in the provided fields, based on the table below:
Field | Description |
---|
Field | Description |
---|---|
Is Default | Select Yes to set the workspace name as the default format. Note: If the workspace name is not specified in the CSV file uploaded via the Jobs tab or in the SQL file uploaded via the Data Uploader, the workspace name set as default here, will determine the workspace name format. |
Rule | Enter a name for the rule |
Format | Enter a format for the workspace name to displayed. A sample rule is displayed as the placeholder in the format field. Tip: The naming format is suggested as "Client ID- Matter ID- Matter Name" {@ClientId@ - @MatterId@ - @MatterName@} |
Metadata | Displayed if No set as default option. Select the metadata from the drop-down. The metadata drop down will display both the metadata name and the display name added. To assign a metadata, either click the drop-down menu and select from the list or manually enter the value, which will auto-complete if it is assigned in Administration>Metadata. In the corresponding text box, type the metadata value to be matched for the rule to be applied. To add more than one metadata to the rule click the '+' sign at the end of the text box. Select the search operator from the drop-down. You can also combine the two search operators.
The Workspace rule will only be applied if the search criteria matches with the metadata defined here. |
Click Save.
The list of information is displayed in the following columns:
Column Name | Description |
---|
Column Name | Description |
---|---|
Rule | The rule name entered above. |
Format | Workspace name format specified above |
Is Default | Is updated based on selection made when adding workspace name |
Action | Click to edit the workspace name and rules. The Edit Rule Creator window is displayed. Make the necessary changes and click Update. Click Delete to delete the rule setup. |
Template Rules
To define the iManage template names rules and format to be applied:
Click the iManage tab.
In the panel for Template Rules click the Add New button.
In the window for Rule Creator, type information in the provided fields, based on the table below:
Field | Description |
---|
Field | Description |
---|---|
Is Default | Select Yes to set the workspace name as the default format. Note: If the template format is not specified in the CSV file uploaded via the Jobs tab or in the SQL file uploaded via the Data Uploader, the template set as default here will be applied to the workspace created. |
Template | Select a template from the drop-down. The drop-down will include all the templates created in Administration> Template Editor. To remove a template click the x. |
Rule | Enter a rule name |
Metadata | Displayed if No set as default option. Select the metadata from the drop-down. To assign a metadata, either click the drop-down menu and select from the list or manually enter the value, which will auto-complete if it is assigned in Administration>Metadata. In the corresponding text box, type the metadata value to be matched for the rule to be applied. To add more than one metadata to the rule click the '+' sign at the end of the text box. Select the search operator from the drop-down. You can also combine the two search operators.
The following operators are available:
The Template rule will only be applied if the search criteria matches with the metadata defined here. |
Click Save.
The list of information is displayed in the following columns:
Column Name | Description |
---|
Column Name | Description |
---|---|
Rule | The rule name entered above. |
Template | The template selected for the rule. |
Action | Click to edit the template rules. The Edit Rule Creator window is displayed. Make the necessary changes and click Update. Click Delete to delete the template URL |
Folder Metadata
Use the Default Folder Metadata section to add all the folder metadata that will be inherited from the workspace level.
Click the iManage tab.
In the panel for Default Folder Metadata click the Add New button.
In the window for Add Default metadata, type information in the provided fields, based on the table below,
Field | Description |
---|
Field | Description |
---|---|
Metadata | Select the metadata from the drop-down. To assign a metadata, either click the drop-down menu and select from the list or manually enter the value, which will auto-complete if it is assigned in Administration>Metadata. The metadata selected here will be applied to all the default folders in iManage. |
Note: The default folder metadata set here only applies to folders and does not copy down to the search folders. Client and matter metadata must be specified on the search folders specifically. Read here for instructions to add search folders.
Click Save
The list of information is displayed in the following columns:
Column Name | Description |
---|
Column Name | Description |
---|---|
Metadata | Folder Metadata selected above. |
Action | Click to edit default metadata. The Edit Default Metadata window is displayed. Make the necessary changes and click Update. Click Delete to delete the default metadata. |
Group Rule
To define the default group security to be applied to the workspaces created in iManage.
Note: If more than one rule matches the criteria then matched groups will be added to the workspace ACL.
Click the iManage tab.
In the panel for Default Group Rules click the Add New button.
In the window for Edit Rule Creator, type information in the provided fields, based on the table below:
Field | Description |
---|
Field | Description |
---|---|
Is Default | Select Yes to set the workspace name as the default format. Note: If the Group rule name is not specified in the CSV file uploaded via the Jobs tab or in the SQL file uploaded via the Data Uploader, the group rule set as default here will be applied to the workspace created. |
Metadata | Displayed if No set as default option. Select the metadata from the drop-down. To assign a metadata, either click the drop-down menu and select from the list or manually enter the value, which will auto-complete if it is assigned in Administration>Metadata. In the corresponding text box, type the metadata value to be matched for the rule to be applied. To add more than one metadata to the rule click the '+' sign at the end of the text box. Select the search operator from the drop-down. You can also combine the two search operators.
The following operators are available:
The Template rule will only be applied if the search criteria matches with the metadata defined here. |
Let's Connect📌
☎ +1 630.598.1100
☎ +44 20 3880 1550
📧 support@litera.com
💻 https://www.litera.com/support/
📝 Support is available:
4 am - 8 pm US Eastern
(9 am - 1 am GMT/BST
7 pm - 11 am AET) on normal business days (excluding holidays)
© 2024 Litera