Collection

A collection is the complete framework for a particular entity type — holding both the definition of what that entity type is and every instance of it. Every distinct thing in your organisation that can be uniquely identified has its own collection: customers, businesses, team members, flows, tasks, products. If it's a thing that exists more than once and needs to be tracked, it lives in a collection.

Collections are the foundational layer of Decidr's data architecture. When you define a customer entity type, the collection holds the schema — what attributes a customer has, how it relates to other entity types — and every individual customer record. The same applies to every other entity type in your organisation. A flow has a collection. A task has a collection. A team member has a collection. Everything unique and repeatable in your business has a structured home.

Without collections, your organisation has no consistent way to define what things are. The same entity type ends up described differently across tools, teams and apps — leading to conflicting data, broken automations and intelligence that can't reason across your business coherently. Collections establish the single source of truth for each entity type, so every app, flow and decision draws from the same definition.

Every entity type your organisation uses has its own collection — from the obvious to the granular:

• A customers collection holding both what a customer is and every customer record
• A tasks collection defining the task schema and containing every task instance across every flow
• A team members collection that every app can reference when assigning ownership or routing work

A collection is where your organisation defines what something is and keeps every instance of it.