Clio Operate User Account: iManage integration
Clio Operate integrates with iManage using an OAuth2 flow, where users are authenticated against the iManage REST API.
Clio Operate provides the ability to either link a single 'service account' user, which all users access iManage as, or to link individual user accounts, allowing Clio Operate to interact with iManage as those users.
However, there are areas of functionality within Clio Operate that interact with iManage without a user context. If you require these areas of functionality to operate, then you need to consider having a Clio Operate user account in iManage that has the appropriate permissions.
The table below describes functionality in Clio Operate that interacts with iManage.
Wherever it is possible to interact as an individual user, you may choose to link users or simply allow a Clio Operate user account to perform all of these actions.
Where it is not possible to interact with iManage using a user context, the permission requirements for the Clio Operate service account are described.
A note on auditing
Regardless of whether there is a user context or not, the audit trail within Clio Operate will show where a user performed the action. Not having individual user accounts linked only limits the audit that iManage will receive, as these actions will be shown as being completed by a Clio Operate user account.
Functionality |
Can interact as a user context |
Permission Requirements |
Notes |
Directory browsing |
Yes |
The user must have permission to view the iManage workspace and documents within it. |
This applies to workspaces that are used to store documents for matters, for workspaces where document templates are managed etc. Wherever a user needs to view a workspace from Clio Operate they need to have permission in iManage to view this workspace.
|
Opening and Previewing documents |
Yes |
The user must have permission to view the iManage workspace and documents within it.
|
|
Copying and Moving documents |
Yes |
|
|
Uploading documents |
Yes |
The user must have permission to add documents to the iManage workspace.
|
|
Creating folders |
Yes |
The user must have permission to create folders in the iManage workspace.
|
|
Monitoring Inbound Email |
No |
The Clio Operate service account needs permission on a workspace where it can store email attachments before they are filed.
|
Clio Operate has functionality where it can monitor inbound email address(es).
Emails arriving are ingested into Clio Operate and become Inbound Email work items. Allocation rules can be set to determine which teams or individuals should receive the email work item in their queue.
When ingesting emails, Clio Operate will separate out the attachments from the email. Clio Operate needs to store these in a document repository (which may be iManage) until the user files the documents against a case, or completes the inbound email work item.
|
Document Filing |
No |
The Clio Operate service account needs permission on the source and destination workspace. |
Documents may be filed from email attachments or inbound emails to be stored in the document repository for a matter.
|
Document Generation |
Yes |
The user must have permission to view the documents in the document template repository (which may be in iManage). The user must have permission to store documents in the workspace that is defined as the output path for the document. |
The location used to store document templates and the location where the generated documents are stored can be completely different Document Management solutions.
Most customers simply define a "Clio Operate document templates" workspace in iManage, but it is possible to store these in an alternative DMS. |
Document Bundling |
No |
The Clio Operate service account needs permission on the matter workspace that it is getting the source documents from and saving the generated bundle to |
Clio Operate provides functionality to generate several documents from different templates and 'bundle' these as a single document, usually a PDF.
|
Document Splitting |
Yes |
|
Clio Operate provides functionality to split large documents into several smaller documents and store these separately, in separate locations.
|
Outbound Emails |
Yes / No |
The Clio Operate service account will be used to retrieve attachments on outbound emails from the DMS.
The Clio Operate service account needs permission to the matter workspace in order to save the outbound correspondence. |
Clio Operate can store a copy of any outbound email sent from a case into the document management system.
|
PDF Conversion |
Yes / No |
|
In the user interface it is possible to convert compatible documents to PDFs. This will use a user context.
As part of post-processing for creating a document, document bundle, sending an email with attachments etc. it is possible to specify that the documents are converted to PDFs and archived. This cannot use a user context.
|
Post Room Delivery |
No |
The Clio Operate service account needs permission to the workspace designated for post room delivery. |
Clio Operate provides functionality to 'deliver' documents via post, by placing these in a DMS location. This process is done by the service account. |