Integrating iManage with Legatics enables seamless document transfers between the two platforms, enhancing efficiency and improving document security. This guide provides a comprehensive walkthrough for setting up and managing the iManage integration, whether you're using Cloud iManage or an on-premise server.
Tip: To understand how the integration works for users, read this article
Overview
Integration approach
Using iManage’s Universal API, a direct connection is created between Legatics and your iManage Work environment. This requires bi-directional network access to iManage. So the connection crosses your firewall.
Note: If you need a technical understanding of how the integration works, consult our security whitepaper or our dedicated iManage overview document (both available by contacting your account manager).
Core features
Multiple servers: You can connect multiple iManage servers to Legatics
Support for Cloud and on-premise: You can connect Cloud iManage and on-premise installations
Support for subdomains: If your Cloud iManage has a subdomain, we can support it.
Restrict to members: You can restrict what Members can use the integration
Server types
iManage has different types of servers. The differences are set out below.
Note: It's important to understand the differences, as it impacts how you integrate iManage with Legatics
| Cloud iManage | On-premise |
Explanation | iManage's new multi-tenanted cloud system | iManage's older "Work Servers" that are either hosted:
|
URL endpoint |
|
|
Adding apps in iManage | Select from list of registered applications | Manually through a installation package |
Limitations
URLs can't be edited after creation: Once set, URLs cannot be edited. If incorrect, the server must be removed and re-added.
Port specifications: URLs cannot include arbitrary ports without additional configuration. Contact support for assistance.
Firewall access: Ensure that your firewall permits Legatics to access iManage by allowing traffic from Legatics' IP address (contact us at support@legatics.com to obtain this).
No auto-sync: We don't automatically synchronise versions between Legatics and iManage. This is deliberate, to ensure users are only uploading new versions (and exposing them to external participants) when ready.
Connecting to Cloud iManage
This section only applies if your iManage is hosted on Cloud iManage (ie with an endpoint of cloudimanage.com).
Step 1: Add Legatics as an application in iManage
Tip: This work is done in iManage. Consult their help articles for detailed guidance
Navigate to iManage Control Centre
Navigate to Applications in Settings
Select Add Application
Find and select Legatics 2 in the list of applications
Select Authentication > Access > Review > Finish
Step 2: Add Cloud iManage to Legatics
In the Admin System, go to Integrations > iManage and press Add server
In the pop-up that appears, select "Cloud iManage" and enter:
a name for the iManage server
the subdomain of the iManage server (if applicable)
Press Add server
Tip: The server name only appears to users if you have multiple servers connected
Your server is now connected, but isn't available to users. At this point you may want to make configurations (see below).
Connecting to on-premise iManage
This section only applies if your iManage is not hosted on Cloud iManage (ie the endpoint is not cloudimanage.com).
Step 1: Add Legatics as an application in iManage
Tip: This work is done in iManage. Consult their help articles for detailed guidance
Step 1A: Generate a YAML file
1. Create a .txt file
2. Copy and paste the below information into the .txt file and complete the placholders in api_key and redirect_URL
id: legaticsapp
name: Legatics 2
api_key: [INSERT HERE]
publisher: info@legatics.com
organization: Legatics Limited
version: '2'
redirect_url: https://api.{legatics_URL}/auth/v0/oauth2/authorized
Note:
API key: You'll need to generate this. Keys must be unique and 32 digits long
Legatics URL: This depends on the Legatics instance you're using. You can find your URL from the accounts page (don't exclude https://)
3. Save the .txt file as a YAML file. To do this:
Click on the file
Select Save as from dropdown
Name the file
legaticsapp.yamlSave as type "select all files"
4. Save the txt file into a ZIP folder with the name mainfest.zip
Step 1B - Configure iManage with YAML file
1. Navigate to iManage Control Centre
2. Navigate to Applications in Settings
3. Select Add Application > Upload package
4. Upload the YAML file you created above
5. Select Authentication > Access > Review > Finish
Note: Record the client secret and client ID that was generated. You will need it for step 2.
Step 2: Add on-premise iManage to Legatics
In the Admin System, go to Integrations > iManage and press Add server
In the pop-up that appears, select On-premise and populate the details
Press Add server
You can input the following details when adding the server:
Name | This only appears to users if you have multiple servers connected |
URL | The base URL of your iManage server. For example
Note that:
|
API URL | This is optional.
Adding an API URL gives you the ability to make the REST API accessible to the Legatics backend, while having the iManage file picker and authentication endpoints accessible only from within your network (including any remote worker VPN provision).
This can help to improve the security position of the integration. This is because the user must authenticate and initiate transfers when on your network and only after doing so can the Legatics backend communicate with the iManage API to undertake the transfers. Consult our dedicated guide for more information. |
Client ID | This is generated in iManage as part of step 1B |
Client Secret | This is generated in iManage as part of step 1B |
Your server is now connected, but isn't available to users. At this point you may want to make configurations (see below).
Configuring an iManage server
Once your iManage server is connected, you can configure it in a number of ways. The section below sets out the configurations available.
Note: Configurations can be made to enabled and disabled accounts
Restricting access to specific Members
Your iManage server is only available to your Members (across the entire instance). You can further restrict what Members can use the iManage integration for a specific server.
Caution: We only recommend using this feature when you're testing that the integration is working as expected.
To restrict a server to specific members:
Go to the iManage server you want to edit and toggle Restrict to specific members
Search for the Members you want to restrict the server to (you can search by user name or email) and press on the Member.
Repeat this for any additional Members
Press Save to apply your changes
Enabling the server
Once you're happy with how the server is set up, you need to make it available to users. To do this press the toggle at the top right of the server. This will make the server visible to your users.
Disabling the server
To disable a server, find the server you want to disable and press the disable toggle in the top right of the server screen.
When you disable a server, users won't be able to push/pull documents from it. But the links to documents in iManage are retained. So if you re-enable the integration, the user will see those links again.
Removing the server
To remove a server, find the server you want to remove and press the remove server button in the bottom right of the server screen and press remove server in the pop-up that appears.
This will remove the server from Legatics. The links to those documents are removed, but the documents in Legatics are retained.
Troubleshooting
You're unlikely to run into troubles when connecting with Cloud iManage. Issues are more likely to occur when you're connecting to an on-premise server.
Note: We've got more technical details for your network administrator about the source and destination ports, and our IP address. Contact us at support@legatics.com to obtain this.
Content is blocked
You try to get a file from iManage or save a file from iManage, a window opens and says "This content is blocked"
This is likely to be caused by your internal security settings, such as a browser security setting, network firewall, or content filter.
To fix it:
Check with your network administrator and ensure that traffic from Legatics to your iManage server is not being blocked by a firewall or proxy
Ensure that necessary ports are open for communication between the Legatics and the iManage server.
We've got more technical details for your network administrator about the source and destination ports, and our IP address. Contact us at support@legatics.com to obtain this.
Something went wrong
You try to get a file from iManage or save a file from iManage, a window opens and says "error.somethingWentWrong"
This is most likely caused by:
Incorrect URL settings
Firewall or proxy blocking
To fix it:
Verify that the URL is correct and points to the correct server and port, and ensure that any required paths or endpoints are correctly specified
Check your firewall and proxy settings to ensure that traffic to and from the Legatics server is allowed.