Properties
A property is a field that every entry in a collection can fill, such as Distance in Workouts or Rating in Books.
A collection and its properties are the shape of your data. The entries are the data. Each entry has one value for each property. See How your data is organized.
An example
The Workouts collection has four properties. Each entry fills them in its own way.
| Property | Type | “Morning run” | “Push day” |
|---|---|---|---|
| Distance | Number, in km | 5.2 | (empty) |
| Duration | Number, as a duration | 32 min | 45 min |
| Type | Tags | Run | Strength |
| Felt | Number, shown as stars | 4 of 5 | 3 of 5 |
The first two columns are the shape: the same for every workout. The last two columns are the data: one value per property, for each entry.
An empty value is allowed. “Push day” has no distance, and that is fine.
Each property has a type
The type decides what the field holds and how you edit it: a number, a date, a tick, tags, a link to another entry, and so on. There are 14 types. See Property types.
Two types hold blocks (a paragraph, a photo, a chart): Block page, for writing from top to bottom, and Dashboard, for tiles you drag and resize. See Block pages and dashboards.
Properties belong to one collection
A property lives directly in its collection. Workouts has its own Distance, and Books has its own Rating. There is no shared list of properties that several collections use.
To show several collections side by side, a global collection matches their properties up.
Fields that are not properties
Every entry also has built-in fields: Title, Icon, Entry date, Created at, Updated at and Parent. They are always there, and you cannot remove them. See Entries and System fields.
Add, rename, change, remove
| You want to… | What happens |
|---|---|
| Add a property | Every entry gets the new field, empty. If the collection already has a property with that name, the new one gets a number: a second “Distance” is called “Distance 2”. |
| Rename it | The new name shows everywhere at once. A name the collection already uses gets a number, the same way. Views, card designs, formulas and automations keep working, because they point to the property’s id (a fixed number), not its name. The files in your folder get the new name too. |
| Change its type | Values that convert are converted. Values that do not convert are cleared; the dialog says how many first, and one Undo brings them all back. See Changing a property type. |
| Remove it | The field leaves every entry. An Undo toast lets you take it back. |
| Reorder it | The entry page shows properties in your order. |
Two properties in one collection never have the same name, so a name always points to one field (in a formula, in a file, for the AI).
If a change cannot be saved, the app puts the old value back on the screen and says so in a short message. A change is never lost without a word.
Starting values
A property can have a default: the value a new entry starts with. You can change it on the entry later.
To set it, open the collection’s Properties tab and click a property’s row. Each row shows only the property’s icon, name and kind; the default and the other details are in the settings panel that opens.
| Default | A new entry gets | Example |
|---|---|---|
| A value | that value | Unit: “g” in Meds & supplements |
| A formula | the formula’s answer, worked out once, for the entry’s own date | Day: formatDate(today(), "iso") gives “2026-03-04” on an entry dated 4 March, even if you make it on 9 March |
| A list of sub-entries (only a Children property) | the entries inside it | a new Morning Routine starts with its 6 checklist items. See Children. |
A preset value wins over a default.
Where a property shows
- On the entry page, with the standard editor for its type.
- In views, as a column, a card field or a group.
- On cards, only where you place it in the card design. A field you do not place stays on the entry page. See Card and row designs.