Databases & structured data

A database feature lets you store information as records with defined fields, such as a client with a name, status, owner and renewal date, instead of loose text on a page. The same records can then be shown in different ways: a table, a kanban board, a calendar or a gallery. Notion is a well-known example, where a database sits inside a normal document workspace.

Businesses run on lists: clients, projects, content ideas, candidates, assets. In a plain document those lists go stale and cannot be filtered. A database keeps each item in one place, lets different people see their own slice, and removes the need for a separate spreadsheet next to the documentation.

It suits teams that want lightweight tracking next to their notes and processes. It is not a replacement for a real relational database or a CRM, which handle larger volumes, strict permissions and automation more reliably.

• Which field types exist, and can records link to records in other databases?
• Can you filter, group and sort views, and can each person save their own view?
• How does it behave with a few thousand records?
• Can you import from a spreadsheet and export again if you leave?