Document collections : Opus 2 Platform

Minimum Software Version	8.18.10
Solution(s)	Hearings ⨉ Cases International ✓ Cases US ✓ Institutions ⨉ Counsel ✓

Explains what document collections are, the types available, how numbering and metadata work, and how to manage access on collections in Opus 2.

A collection is a named group of documents that are conceptually related. Documents added to a collection are linked virtually and remain in their original folders — a single document can be included in multiple collections simultaneously without duplication. Within a collection, a document is referred to as a collection item, while the original file remains the source document in its folder. Collections allow users to create structured groupings such as bundles or binders without impacting the underlying document structure.

Types of collections

Unnumbered collections

Provide a top-level container for documents with an optional hierarchy of sub-sections. Documents are identified only by their source document properties.

Example: Grouping background correspondence and research papers for internal review.

Numbered collections

Add identifiers (section numbers and/or document numbers) and are used to create formal bundles or binders. Hierarchical numbering concatenates parent and child numbers.

Example: A hearing bundle organised as A/1/1, A/1/2, A/2/1.

Numbered collection configuration

Numbered collections can be configured when created or later via Edit Collection, provided Number sections or documents is toggled on.

Property	Applies to	Description
Collection number/delimiter	Collections	Primary identifier (numbers, letters, or mixed). Delimiter defines the separation (for example, `/` or `.`).
Number/delimiter	Sections	Identifier for individual sections (only if numbered individually).
Sections	Collections	Manual or sequential numbering (numeric, alphabetic, Roman).
Sub-sections	Sections	Manual or sequential numbering inherited from the parent section.
Documents	Collections and sections	Unnumbered or sequential numbering for documents.
Inserted documents	Collections and sections	Special numbering for documents added after numbering is locked.
Pages within documents	Collections and sections	Restart page numbers per document or continue across documents.
Number sections individually	Sections	Allows each section to define its own numbering.
Include as part of parent sequence	Sections	Items numbered as if they were directly in the parent section.

Collection-specific metadata

Collections can apply metadata directly to collection items without modifying source documents.

Assign one or more document types to a collection.
Enter metadata values per collection item.
Collection-level values override source document values.

Example: Assigning a Bundle Role field to collection items while retaining the original document metadata.

Annotations on collection items

Annotations on source documents are not reflected on collection items.
Annotations made on collection items can be configured to apply to the source document, or apply only within the collection.

This behaviour is controlled via the collection's annotation settings.

Deleting collection items

Removing a document from a collection does not affect the source document. Deleting a source document causes it to appear as not available in the collection.

Managing access on collections

Collection-level access

Access can be restricted to specific users or groups, set during Create Collection or via Set access. Restricted collections show an eye icon. Sections inherit access from their parent by default but can be overridden.

For more information, see Setting access on collections.

Editing collection access

Select the three-dot (⋯) menu on a collection or section.
Select Set access.
Add users or groups using the appropriate icons.
Remove access using the cross icon.

Hover over the eye icon to see who currently has access.

Access control on documents within collections

Scenario 1: Source documents restricted, collection open to all. Users without access to the source document see it listed as not available. Useful for confidential documents included for structural completeness.

Scenario 2: Source documents and collection open, document restricted at collection level. Restricted users do not see the document in the collection. Useful for draft documents shared privately before wider release.