For multi-region organizations, iManage Insight+ lets users search across all regions and libraries within the firm. Users can search for documents, matters, and other data regardless of where it’s stored, subject to their permissions.

NOTE: If your organization implemented iManage Insight+ before May 5, 2026 and you wish to enable multi-region search, contact your Partner or iManage Cloud Support.

Each iManage Work library is tied to a single region. Global firms use multiple libraries to stay compliant with data residency laws. To keep those requirements intact, customers can use multiple iManage Work and Knowledge libraries, so submitted content remains in the same jurisdiction.

Multi-region indexing and search

iManage Insight+ uses separate regional indexes for each customer. Each index stores documents from all Work Libraries and Knowledge Libraries assigned to that region.

Searches are run across regional indexes based on the filters in each query. Insight+ analyzes those filters and limits the query to only relevant indexes. This gives prompt and accurate results for users.

Users can choose their search query language through User Settings (currently supports: English, French). Selecting a search query language affects how matches are found. It doesn't impact availability of documents for searches across regions. For example: if a user set their search language as French, they could still find documents from the US or UK libraries (subject to their permissions and depending on their query terms).

NOTE: If your organization is moving from a single-region setup to a multi-region setup, then you'll need to submit the list of Libraries that require indexing to iManage Customer Support.

  • Submit the list of Knowledge Libraries that require indexing to iManage Customer Support.

  • All available libraries can be indexed.

  • When indexing is complete, iManage Customer Support must be informed about the following:

    • Libraries to be enabled for search in Insight+

    • Libraries to remain hidden from search results

  • The libraries won’t get displayed for search until indexing is complete and the library is made available for search.

  • Only libraries confirmed as enabled for search, will show in search results for the users.

Configuring user profiles and default filters for Multi-region search

Where an organization is multi-region, you can target User profiles with Default filters to improve relevance for users in different locations. For example, you can limit the search of a user in the UK to the UK Library by default. The user can choose to widen the search if required.

Multi-region search pulls queries from multiple regional libraries across the organization, and shows relevant results from all libraries available for search.

For more information about how User profiles and Default filters work, refer to User profiles and Default filters.

Configuring Knowledge Libraries for regions

Curators can operate independently by region, using different workflows as needed.

  • Each region can have its own dedicated Knowledge Library. For example, UK Knowledge Library, US Knowledge Library, EU Knowledge Library, and others.

  • Each Active library is linked to one Knowledge library.

  • Submitted documents are copied only to the linked library.

  • Multiple Active Libraries can share a single Knowledge Library, or each region can use separate Knowledge Libraries.

  • To maintain data residency of a submitted Knowledge document, you should pair a knowledge library with each regional active library, so that content stays within its required jurisdiction.

Metadata in Multi-region search

Each Knowledge Library has its own metadata schema. If users search across regions, we strongly recommend that you use one shared schema across your Knowledge libraries to avoid duplicate filters and a poor user experience.

For example, Knowledge Library A uses UK as a value for the Jurisdiction field. Knowledge Library B uses ‘England & Wales’. Users will have to check both values, rather than just one value. Same with the fields themselves. If Knowledge Library A uses Jurisdiction as a field but Knowledge Library B uses Country, both filters and their values will get displayed. Spelling errors and typos will have the same effect. This can lead to confusion, fragmentation of information, and poor user experience.

If users search only locally, matching schemas aren’t required.

Locale-specific search values

Some metadata fields show different names in different regions for search values. These localized values are optional and apply to Lookup, Taxonomy, and certain String fields. Matches for their region will be displayed to users, so they won’t get the wrong results.

Let's consider an example where the value for en_GB is Share Purchase Agreement and for en_US, it’s Stock Purchase Agreement. If User A with English (UK) selected as their default language in the User settings enters Stock, they won't see matches in that field. Only when they switch to English (US) language settings, the match for Stock displays.

iManage Work doesn't support localized values for documents. You can't add them to Knowledge or Active document metadata schemas.
If Knowledge documents are linked to a Matter, you can add Matter fields as facets or filters in Knowledge search. Matter fields do support localized values. So while document metadata itself can’t be localized, you can still give users localized filtering through Matter metadata.