Collections

Collections are lightweight databases inside a repository (G B): you define the fields, add records, and view them as a table. A CRM, a content calendar, a hiring pipeline, a hardware inventory; anything that is rows-and-columns shaped but does not deserve a separate product.

Create a collection

Start from a template (CRM contacts, for example) or from scratch with your own fields. A collection has a name, an icon, and a schema you can change at any time; adding a field never requires a migration, because records store whatever fields they have.

Field types

Type	Holds
Text, long text	Short strings and paragraphs
Number, checkbox	Quantities and flags
Select, multi-select	One or many options from a list you define
Date	Dates, with sensible display
URL, email, phone	Typed contact fields
Person	A member of your organisation
Relation	A link to an issue, doc, or another record
Created / updated time, created by	Maintained automatically

Views

The table view filters, sorts, and groups by any field, with inline cell editing. Filtering happens client-side over live data, so slicing a thousand records is instant and updates as teammates edit.

Records

Open a record for the full panel: every field plus a collaborative body, the same editor as documents. Use the body for the prose that belongs to a row: meeting notes on a CRM contact, the brief behind a content-calendar entry.

Relating records to work

Relation fields connect records to the rest of the platform: a bug-report record points at the issue tracking it; a launch checklist points at the PRs that ship it. Both ends show the link, because records are nodes in the same relation graph as everything else.