Data · Models and relationships
Data layer
Give every operational record, relationship, file, and label one dependable structure.
Read the technical documentation
Models
Models give every team a shared definition of the records they use: customers, sites, requests, contracts, payroll runs, or any other part of the operation. Fields can carry operational values, dates, money, files, structured choices, and human-readable labels.
Because the model ships with the workspace, apps, policies, and logic all agree on the same data shape and record history.
Relationships
Relationships connect records without duplicating them across tools. They preserve context as work moves between teams and let every interface follow the same operational graph.
One versioned model
- Typed fields and files for day-to-day operational records
- Relationships shared by apps, logic, and policies
- Record labels used consistently in links, search, and selectors
- Revision history that supports approvals, audits, and rollback
Builders group models into collections under src/collections/<name>/+model.ts and define relationships in src/collections/+relationship.ts as reviewable Pod source.
Continue through the product
Security
Keep policies, approvals, and audit history in the workflow itself.