Collections

Collections turn your content into clear, navigable experiences. Use them to group related items, build feeds, and highlight what matters for each audience.

What you can do with Collections:

• Create logical groupings (by topic, audience, or series)
• Deliver personalized feeds for different segments or profiles
• Curate seasonal or sequenced sets (like weekly highlights)
• Power navigation and featured sections across your apps

Collection Types

Every collection has a type that determines its role:

• Root: The top-level entry point of the content tree.
• Folder: A container for organizing content hierarchically, similar to a file system folder.
• Standard: A general-purpose collection for grouping related content.
• Queue: A collection that processes items in order.
• System: A system-managed collection not directly visible to end users.

Items and Ordering

Collections can contain both child collections and metadata items. Each item relationship can carry its own custom attributes.

Ordering is configurable per collection. You can sort by field name, JSON path, attribute location (item or system), and direction (ascending or descending).

Language Variants

Collections support localization through language variants. Each variant provides a localized name, description, and attributes. Variants can have independent workflow states and visibility settings, so a collection can be published in one language while still in draft in another.

Supplementary Content

Collections can have supplementary files attached via unique keys. Each supplementary item tracks its content type, storage details, and upload status. Pre-signed URLs are provided for direct upload and download.

Permissions

Access is controlled through group-based permissions. Each collection can define which groups have view, edit, or manage access. Public visibility is controlled separately for the collection itself, its item list, and its supplementary content.

Locking

Collections can be locked to prevent modification. Items within a collection can also be locked independently, allowing the collection's own attributes to change while its membership stays fixed.

Soft Delete

Collections use soft delete by default. Deleted collections can be recovered or permanently removed.

Templates, Categories, and Traits

• Templates: Collections can reference a template that defines default attributes, ordering rules, and filters.
• Categories: Assign categories to collections for classification and filtering.
• Traits: Assign traits to collections for additional behavioral tagging.

Workflows

Collections participate in the same Workflow system as metadata. State transitions, pending states, and time-based validity windows all apply to collections.

Why teams rely on Collections:

• Quick to organize and reuse across channels
• Works hand-in-hand with Metadata and Workflows
• Scales from a handful of items to thousands without losing structure