Search helps locate documents. It doesn't tell a knowledge worker which ones matter, in what order, or why.

Knowledge Collections help close that gap. In iManage Insight+, a Knowledge Collection is a curated, structured set of Knowledge documents that an administrator can assemble around a specific matter, practice area, or recurring piece of work. A Knowledge Collection can have a precedent book of an organization's filings, a step-by-step process for executing a transaction, a process guide for a recurring advisory question, or a single source of truth for a client's approved templates.

While a Knowledge tab holds the organization's knowledge documents, Knowledge Collection draws from that library and presents a curated subset, with structure, sequencing, and commentary that the source documents alone cannot provide. Some collections are built for knowledge workers to browse directly, whereas some exist so an AI tool can complete tasks such as drafting, summarizing, or an assistant tool. Knowledge Collections can help AI draw information only from an organization's approved content instead of generic sources.

For administrators, creating Knowledge Collections is primarily a curation and governance responsibility to ensure quality, manage risk, and drive profitability. Creating a collection means selecting a knowledge library, assembling documents, adding quick links and usage notes that explain what to use when and why, and organizing them into groups. That's why the value of a Knowledge Collection depends on its initial setup. So it's important for administrators to establish proper structure, metadata, and context correctly.

To set up Knowledge Collections: