Connecting Clio Operate to iManage Cloud

A guide for customers and partners integrating with cloudimanage.com

Overview

This article describes the steps required to connect Clio Operate to iManage Cloud (cloudimanage.com). It covers the full integration process — from registering your environments through to testing — and includes variant guidance for specific scenarios.

Read this article if:

You are connecting any Clio Operate environment to cloudimanage.com for the first time.
You are adding new environments (UAT, training, production) to an existing integration.
Your iManage URL is a custom subdomain such as https://yourfirm.cloudimanage.com (a "vanity URL").
Your Clio Operate version is below 7.11.0 and you need to configure the integration using the hosted iManage workaround.

For general background on iManage configuration in Clio Operate, refer to the main Configuring Clio Operate for iManage Integration article in the Knowledge Base.

How the cloudimanage.com Integration Works

When connecting to iManage Cloud, Clio Operate authenticates using OAuth 2.0 against the cloudimanage.com identity platform. Because Clio Operate is a multi-tenant SaaS platform, it uses a shared global iManage application registration.

This has an important consequence: your iManage Customer ID and your clio Operate environment redirect URIs must be added to the global iManage application registration before the integration can function. You cannot do this yourself — it requires Clio Operate Support to submit a request directly to iManage.

Unlike some integrations, the iManage Cloud registration step cannot be self-served. Your Clio Operate environments will not be able to authenticate with iManage until this registration is complete.

Allow 24–48 hours for iManage to process the registration once it has been submitted.

Process Overview

The following steps are required for any cloudimanage.com integration. Complete them in order.

Step	Action	Responsible
1	Gather your iManage Customer ID and environment URLs	Client / Firm
2	Contact Clio Operate Support to request iManage registration	Client / Firm
3	Clio Operate Support submits registration request to iManage	Clio Operate Support
4	Await registration confirmation (24–48 hours)	iManage
5	Configure the iManage linked service in Clio Operate	Client (with guidance)
6	Link a fall-back iManage user account	Client
7	Test the integration	Client

Step 1 - Gather Your iManage Customer ID and Environment URLs

Before contacting Clio Operate Support, gather the following information:

iManage Customer ID

Your iManage Customer ID is a unique identifier assigned to your firm by iManage. It is required for the application registration and is distinct from your login credentials or firm name.

Your iManage Customer ID will typically appear in:

Onboarding documentation provided by iManage
Support tickets or correspondence from support@imanage.com
Your iManage administration portal

If you are unsure, contact your iManage administrator or raise a support ticket with iManage to confirm.

Your Clio Operate Environment URLs

You need to provide the redirect URI for every Clio Operate environment that will connect to iManage. This includes all production, UAT, training, and test environments.

Redirect URIs follow this format:

https://<your-environment-url>/externalServices/replyFrom

For example, if your production environment is https://acme.clioweb.com, the redirect URI is:

https://acme.clioweb.com/externalServices/replyFrom

Include all environments — not just production. Each environment must be registered individually. Missing environments will fail with an invalid_redirect_uri error when users attempt to authenticate.

Step 2 — Contact Clio Operate Support to Request Registration

Contact the Clio Operate Support team and provide the following:

Your iManage Customer ID
The complete list of redirect URIs for all environments that will use iManage
Your iManage URL — either https://cloudimanage.com (standard) or your vanity URL (e.g. https://yourfirm.cloudimanage.com)

Clio Operate Support will raise a ticket with iManage to have your Customer ID and redirect URIs registered against the Clio Operate global application registration.

You may receive correspondence directly from support@imanage.com as part of this process. iManage may send confirmation emails or request additional information to complete the registration.

Keep these emails — they confirm that registration has been completed and provide a useful audit trail.

Once the registration request has been submitted to iManage, allow 24–48 hours for it to be processed. The integration will not function until registration is confirmed.

Step 3 — Configure the iManage Linked Service

Once registration has been confirmed, configure the iManage linked service in each Clio Operate environment. Navigate to:

Admin > Integrations > Manage Linked Services (or navigate directly to /admin/oauth)

Add a new linked service and select iManage — Work, or edit an existing iManage service if one has already been created.

Connection setting — All customer environments (production, UAT, training, and test) must use the Sharedo Production connection setting.

The Sharedo Test setting is for internal Clio Operate use only and must not be selected for any customer environment, regardless of whether the environment itself is a test or staging instance.

Standard Configuration (Version 7.11.0 and Above)

On version 7.11.0 and above, the standard iManage Cloud linked service configuration supports all cloudimanage.com setups, including vanity URLs.

In the linked service configuration, select Sharedo Production as the connection type. All customer environments use this connection type.
In the iManage URL field, enter your iManage URL:

Scenario	iManage URL to enter
Standard cloudimanage.com	https://cloudimanage.com
Vanity URL	https://yourfirm.cloudimanage.com (use your actual vanity URL)

Save the linked service configuration.

Vanity URL — If your firm uses a custom cloudimanage.com subdomain, simply enter your vanity URL in the iManage URL field. No additional steps or credentials are required on version 7.11.0 and above.

Configuration for Versions Below 7.11.0

On versions below 7.11.0, the standard iManage Cloud connection type does not support specifying a custom URL. The workaround is to configure the integration using the Hosted iManage connection type, which exposes the URL and credential fields. Functionally, the integration behaves identically — this is a UI limitation only.

If you are on a version below 7.11.0, contact Clio Operate Support before proceeding. The support team will provide you with a Client ID and Client Secret required for this configuration path.

If your iManage URL is the standard https://cloudimanage.com and you are below version 7.11.0, the Hosted iManage workaround is still required to specify credentials.

In the iManage Connection drop-down, select Hosted iManage.
Complete the following fields:

Field	Value
iManage URL	Your iManage URL — either https://cloudimanage.com or your vanity URL
Client ID	Provided by Clio Operate Support
Client Secret	Provided by Clio Operate Support
Preferred Database	The iManage database your firm uses
Redirect URL	https://<your-environment>/externalServices/replyFrom

Save the linked service configuration.

Step 4 — Link a Fall-back User Account

Once the linked service is configured, you must link a fall-back iManage user account. Clio Operate uses this account when communicating with iManage on behalf of users who have not yet linked their own accounts.

In Manage Linked Services, select the Link option on the iManage service.
Sign in using iManage credentials in the authentication window that opens.
Once signed in, the service will display as Linked.

For more detail on fall-back accounts and per-user account linking, refer to the iManage Fall-back and Per-User Account Linking article in the Knowledge Base.

Step 5 — Test the Integration

Once registration has been confirmed and the linked service is configured:

Navigate to Document Administration > Template Explorer.
Confirm you can browse the iManage workspace configured for Clio Operate document templates.
Verify you can create folders and upload documents.

If all three steps succeed, the integration is working correctly.

If you see an invalid_redirect_uri error when authenticating, this typically means one of the following:

The redirect URI for that environment has not yet been registered — allow the full 24–48 hours after the registration request was submitted.
The redirect URI provided to iManage does not exactly match the environment URL (check for trailing slashes or http vs https differences).
The wrong connection type is selected — confirm that Sharedo Production is selected, not Sharedo Test.

Contact Clio Operate Support if the issue persists after the registration window has passed.

Summary — Who Does What

Action	Responsible
Obtain iManage Customer ID	Client / Firm
Compile list of environment redirect URIs	Client / Firm
Contact Clio Operate Support to request registration	Client / Firm
Submit registration request to iManage	Clio Operate Support Team
Provide Client ID and Client Secret (versions below 7.11.0 only)	Clio Operate Support Team
Await iManage registration confirmation (24–48 hours)	iManage
Configure iManage linked service in Clio Operate	Client (with support guidance)
Link fall-back user account	Client
Test integration via Template Explorer	Client

Configuring Clio Operate for iManage Integration
Managing Linked Services in Clio Operate
iManage Fall-back and Per-User Account Linking

Internal use only · Clio Operate Support