Databases
Properties, formulas and rollups
Relations connect databases, rollups calculate across linked records, formulas calculate values from the properties of the same record.
8 min read
On this page
This is about the properties of database records. The properties of pages (under the page title) apply in the whole workspace or only in one space, see Scope.
Edit properties
A click on the column header or View and properties opens the property dialog: name, type (one of 24 property types), options and format. Changing the type keeps existing values as far as they fit. Number formats cover currencies, percent, decimal places and thousands separators and also apply to formulas with a numeric result; date fields show short, long or ISO dates and optionally times. Below the field, + Time shows a time field that starts at 09:00 (on today if there is no date yet); Remove time makes it an all-day date again, and Remove date clears both date and time. Since 0.9.8
If a date needs no time – for example in a form other people fill in – switch off With time in the property dialog. Since 0.10.0 Then + Time no longer appears anywhere for that property: not in the table, the record, forms and surveys, the calendar or quick capture. Values that already have a time keep it and still show it; Remove time stays available for them, but no new time can be added. The dialog shows how many records still have a time. The API and MCP refuse a new time; the CSV import, automations ("Now") and quick capture take the date only. Switched on (the default), everything works as before.
URL, email and phone properties show as links in tables, lists, boards, galleries and records: web addresses open in a new tab (shortened to host and path, the full address in the tooltip), email addresses in your mail app, phone numbers in your phone app. To change one, click the pencil next to the link (on hover or via Tab on a computer, always shown on phones) or the empty part of the cell; Enter saves, Esc discards. Only http:// and https:// addresses, email addresses and phone numbers become links – anything else stays plain text.
Rename and merge options
Records store a select or multi-select value as the option's name. When you rename an option in the property dialog, the dialog lists what changes along with it before saving, for example Rename “Open” to “To do” in 12 records.
- Update records carries the new name everywhere: into the records (also record templates, the trash and form drafts), into the views' filters, groups and board columns, into linked views of the database on other pages and into the database's rules – done rule, workflow, automations, form conditions and the issue sync's status mapping. Records keep their value under the new name; workflow checks and automations don't fire for it. Flowplan first keeps a version in the version history.
- Merge: write another option's name in an option's place and the two are merged (Merge “Done” into “Finished”). The records get the remaining option, which keeps its own rules; the merged option's settings under Status rules and done go away – the dialog points this out.
- Save options only saves just the list; records, filters and rules stay on the old names, as before.
- Formulas are not rewritten: if a formula compares against an option's name (such as
prop("Status") == "Open"), adjust it yourself.
Renaming needs edit access to the property. For the workspace tags, renaming happens under Settings → Tags & properties.
Aliases
The property type Aliases (other names) holds further names of a record, such as "PAC" and "Pompe à chaleur" for the record "Chauffage". A database has at most one such property. In the record you enter the names separated by commas; up to 10 aliases of up to 100 characters each count, surrounding spaces and duplicate names (ignoring case) are dropped.
Aliases work like the title:
- @ mentions and the quick search also find the record by an alias and then show the real title with the alias in grey: "Chauffage · PAC". In the search, aliases weigh as much as the title.
- Unlinked mentions also look for every alias – as a whole word, from two characters, ignoring case. Link keeps the text as written: "PAC" becomes a link to "Chauffage" that still reads "PAC".
- The Markdown export writes them as
aliases:into the frontmatter, the Markdown import readsaliases:andalias:back (Frontmatter).
Filters ("contains", "is"), sorting, formulas (as a list, like multi-select), CSV and the other exports treat aliases as a list of texts. An alias may be used by several records; then both appear. Only people who may read a record find it by its aliases.
Pages keep their aliases under … → Aliases … – see Pages and spaces.
Property visibility
Single properties such as "Salary" or "Internal note" can be limited to certain people. In the property dialog, the Visibility section sets who may read the property and who may edit it:
| Choice | Read | Edit |
|---|---|---|
| Everyone with access (default for reading) | Everyone who may read the database | – |
| Editors and owners (default for editing) | Edit and owner roles | Edit and owner roles |
| Owners only | Owners of the database | Owners of the database |
| Selected groups | Members of these groups | Members of these groups with edit rights |
- Only owners of the database change the visibility; they always see and edit everything themselves.
- Restricted properties show a lock in the column header. Whoever may not read a property does not get the column at all; cells someone may only read are read-only and say on hover who may edit them ("Editable only by …").
- The rules only narrow page and record permissions: whoever may only view the database does not edit a property for "selected groups" either.
- Everyone with access always sees the title property (the first one).
- The server enforces the rules everywhere: in the database itself, in linked views, dashboards, whiteboard cards, exports (Markdown, CSV, JSON, Word, EPUB, print), versions, through the API and the MCP server, for the AI and in calendar subscriptions. It refuses changes to properties someone may not edit – in the record, through bulk editing, import, API, AI or CalDAV – with a message.
- Restricted properties are never public: publications, links with their own permissions, forms, the customer portal and webhooks leave them out, even when a link allows editing.
- Full-text search and the AI's semantic search do not index restricted properties, for anyone.
- Formulas, rollups, AI properties, progress and time that read a hidden property count as hidden for that person as well – their result would otherwise give the value away. A formula with a computed
prop()name depends on every property. A rollup is hidden when the person may not read the property in the target database. - Whoever does not see a property can neither lose nor delete it when changing the schema. Versions of a database with restricted properties are restored by owners only, and records with hidden properties cannot be turned into a page or moved to another database (copying leaves the hidden values out).
Filters and sorting of a view that use a hidden property work on empty values for that person; the condition itself (such as the value compared with) stays stored in the view.
Relations
- Add property → Relation and choose the target database.
- Optionally in both directions: the target database gets a counterpart property, and changes are kept in sync on both sides.
- In the cell, search for records and link them; several links can be removed one by one or cleared together.
Relations appear as links in the record. The database search also finds records by the names of linked records, and relation filters offer these names directly.
Linked records show their icon, in the cell and in the picker. Clicking a linked record opens it in a window over the current table – you stay in your database and return to it with Close. Open in database switches to the record's own database.
Rollups
- Create a relation first.
- Add property → Rollup, then choose the relation and a property of the target database.
- Choose a calculation – 22 are available, depending on the type: original values, unique values, count, empty/not empty (also as a percentage), sum, average, median, minimum, maximum, range, checked/unchecked, earliest and latest date, date range.
Earliest and latest date over Created at or Edited at give an instant in UTC, shown in your time zone. Number rollups appear as a number, progress bar, progress ring or rating, with an adjustable target value. Values from databases someone may not read are not loaded for that person.
AI properties
When AI is switched on, a property can take its value from an instruction to the AI – such as a summary or a category from other properties. Everything about it under AI in databases.
Formulas
Choose the type Formula in the property dialog. The editor offers 58 functions with search, categories, signatures and examples, suggestions while you type and a live preview on a record of your choice.
round(prop("Effort") * prop("Hourly rate"), 2)if(prop("Done"), "✓", concat(format(dateBetween(prop("Due"), today(), "days")), " days"))- References with
prop("Name")stay valid when the property is renamed. - Syntax errors show their position and prevent saving.
- Numeric results are available in filters, sorting, charts and column calculations.
- Date functions calculate in UTC unless a zone is given;
now()andtoday()update every minute. - If a date is empty, date functions return an empty result instead of
#ERROR. In comparisons an empty value counts as 0 – sodateBetween(prop("Due"), today()) < 3also matches records without a date; guard it with!empty(prop("Due")) && dateBetween(prop("Due"), today()) < 3. - Formulas read Created at and Edited at as an instant in UTC (such as
2026-11-05T17:39:02Z), so every date function works with them, e.g.formatDate(prop("Created at"), "MM/DD", "America/New_York"). - Formulas do not run JavaScript; length, nesting and result size are limited.
Function groups
| Group | Examples |
|---|---|
| Logic | if, ifs, coalesce, and, or, not, empty |
| Numbers | sum, average, min, max, round, ceil, floor, abs, mod, pow, sqrt |
| Text | concat, length, contains, replace, replaceAll, trim, slice, lower, upper, format, toNumber |
| Date | now, today, parseDate, formatDate, dateAdd, dateSubtract, dateBetween, year, month, day, hour, timestamp |
| Lists | list, count, at, first, last, join, split, unique, sort, reverse |
The formula editor shows the complete list.