Frequently Asked Questions (FAQs)

The following topics are available:


Why are metadata descriptions hidden in iManage Control Center?
To maintain the security of iManage Work content.

Why are document names hidden in iManage Control Center?
To maintain document security.


What is this feature?

Groups are lists of multiple users. They are a collection for assigning identical privileges and access permissions to certain libraries, workspaces, folders and documents to the group members. For example, if a group has access to a document, the users in the group can access the document.

When does this feature help me?

This feature enables you to add users to a group and provide access to documents. Before providing group access to documents in a library, create the group in the library, and then add the relevant users to this group.

Where can I find this feature?

Navigate to the Access > Groups.


When does this feature help me?

Roles enable you to organize privileges and functions selectively across your organization. For example, a role named Developers can be created and will have each of the privileges granted or denied to fit their function within the organization. All users assigned to the Developer role will have the same set of privileges.

What administrative capabilities are allowed for Tier1 or Tier2 administrators in Control Center?

See Roles for a list of all tiers and their capabilities.

Can I customize Tier 1 and Tier 2 capabilities so that they match my firm's support practices?

Tier 1 and Tier 2 capabilities are designed around best practices for help desk support and cannot be customized.

What are the type of roles supported by iManage?

See Privileges, Roles, and Groups for more details about roles.

Custom Fields

When does this feature help me?

You can use this feature when customer wants to map their set of metadata to the existing custom fields, and also add values to the custom fields so that they can use these values from iManage Work clients.

Can you list the custom fields exposed by iManage Control Center?

Custom1 through custom30. Additionally, custom1/custom2 and custom 29/custom30 each have parent-child relational table (subtables). That means, custom1 can have many aliases directly associated from custom2. For example, if custom1 is Client, and the client is Microsoft, then custom2 could be matters, such as litigation, mergers, acquisitions, Human resources, and Intellectual property cases.

Classes and Subclasses

What kind of document Classes and Subclasses am I allowed to create?

The document classes that you create depend on your company and your library requirements. Document classes can be categorized by genre, department, region, and so on.

What do this Classes/Subclasses contain?

These fields determine:

  • Whether a copy of the document can be echoed to a user’s local hard drive. This is applicable only in DeskSite and FileSite.

  • The custom fields of profile information that are required for the document.

File Handlers

What are these applications, where are they stored, and what type of information do they contain?

Each iManage library has a list of applications associated with it. It contains the information required to integrate document handling applications with iManage Work Server. This information includes the:

  • Procedure to associate document types and applications

  • Program to launch applications from iManage Work Server

When is the information mentioned in the preceding section provided?

When an iManage library created, it is initialized with a common list of applications.


What do the configuration files contain?

The configuration files contain information such as server login information, email management settings, Microsoft Office integration options, and as well as Microsoft Office application specific operations depending on the user settings/preferences. For example, file operations like Open, Save, Save as and so on for Microsoft Office applications like Word, PowerPoint, Excel, Visio, and MS Project. For more information about the Office and email configuration files, see: