Document Collections

What is a Document collection?

A collection is a reusable template that defines which documents a user should submit during a Bynn workflow.

It defines the document requests shown to the user, including which documents are required or optional and which upload, validation, fraud detection, or extraction settings apply to each document. Each collection can include one or more documents, and each document can be configured individually with its own settings.

A collection can include any number of mandatory and optional document requests.

Collections are not launched directly. They are used when selected inside a Document Collection node in a workflow. They are created in the Collections section and then selected inside a Document Collection node in a workflow.


Where it is used

Collections are used in workflows whenever a process needs to request documents from a user.

For example, a collection can be used to request:

  • identity documents
  • licenses
  • bank statements
  • insurance documents
  • supporting files
  • images or camera-captured files

A collection is only used through a workflow. It is not launched or used as a standalone object.

The same collection can be reused across multiple workflows, and a single workflow can include more than one collection if additional document steps are needed later in the flow.


How it connects to workflows

Collections are connected to workflows through the Document Collection node.

When building a workflow, the user adds a Document Collection node and selects which collection should be used in that step. The workflow then controls when the collection is shown and what happens before and after the document submission.

This means:

  • the collection defines which documents are requested
  • the workflow defines when the request appears and how the process continues afterward

Because collections are reusable, the same collection can be selected in different workflows. Because workflows can contain multiple document collection nodes, more than one collection can also be used within the same workflow.


What can be configured inside it

Each collection includes both collection-level settings and document-level settings.

At the collection level, you can configure:

  • Collection Name
  • Description
  • Status

Collections currently support:

  • Draft
  • Active

At the document level, each added document can be configured with:

  • Document name
  • Description / Instructions
  • Document Type
  • Requirement
  • Upload Count
  • File Type Restrictions

Each document can also include additional options such as:

  • Bynn AI Agent Validation
  • Bynn Document Fraud Detection
  • Document Data Extraction

These options serve different purposes: validation checks whether the document meets configured rules, fraud detection checks for signs of manipulation, and data extraction reads values from the document into workflow variables.