Notion looks like a blank page, and for a while that is all most people use it for. Some notes, a few headings, maybe a to-do list. Then someone mentions databases and the whole thing starts to feel like homework.
Here is the reassuring part: a Notion database is just a list where every item has the same set of details attached to it. A list of books. A list of clients. A list of chores. That is the whole idea. Once you can see that clearly, the words thrown around — table, board, property, filter, relation — stop being jargon and start being useful.
What a Notion database actually is
A database is a collection of items, and each item is a page with the same fields at the top. Those fields are called properties. In a reading list, every book is an item, and every book has a Title, an Author, a Status (To read, Reading, Finished) and a Rating.
The difference between a Notion database and a plain spreadsheet is that each row is a full page. Click a row and it opens. You can write notes inside it, paste a quote, drop in an image, or nest another page underneath. The row is not only a line of data; it is a place to think. That is why people end up keeping notes, tasks and projects in databases rather than in ordinary pages.
Notion calls these rows "items" in some places and "pages" in others. They mean the same thing.
One set of records, several views
A single database can be displayed in several ways, and each display is called a view. A view does not copy or move your data. It is a window onto the same records.
- Table view: rows and columns, closest to a spreadsheet. Best for scanning and editing lots of properties at once.
- Board view: cards grouped into columns, usually by a Status or Select property. Best for anything with stages.
- Calendar view: records placed on their dates. Best for deadlines, appointments and publishing schedules.
- Gallery view: cards with a cover image. Best for mood boards, recipes and reading lists.
- List view: a compact list. Best for quick checklists.
Add one from the plus sign beside the database name. The data stays exactly where it is; you have simply changed the angle you are looking from.
Properties: the columns that do the work
Properties give a database its shape. A page with no properties is just a page. Add them deliberately, because a database with fourteen columns nobody fills in is worse than one with four that everyone uses.
The types you will genuinely use:
- Text: free-form. Titles, notes, anything you type. No structure, so filtering is limited to "contains".
- Select: one option from a list you define. Priority: Low, Medium, High.
- Multi-select: several options from a list. Tags, categories, names.
- Status: a select with built-in groups — To-do, In progress, Complete. Boards and progress bars work best with this one.
- Date: with optional start and end times, and a reminder if you want a nudge.
- Checkbox: yes or no. Simple, and surprisingly powerful in filters.
- Number: amounts, hours, scores. Can be formatted as currency, percent or a bar.
- Person: a workspace member. Useful the moment more than one of you shares the database.
- Formula: small calculated expressions built from other properties. Worth learning later, not on day one.
A useful test: if you cannot picture yourself filtering by it, it probably does not need to be a property.
Filters and sorts, without the fuss
Filters decide which records a view shows. Sorts decide the order they appear in. Both belong to the view rather than the database, so you can have one view showing every task and another showing only this week's.
To add a filter, open the view, click Filter, then choose a property, a condition and a value. "Status is not Complete", for example, or "Due date is within the next seven days". You can stack several filters, and Notion will ask whether you want all of them or any of them — that is "and" versus "or". This trips up more beginners than anything else. If a filter is behaving oddly, check that setting first.
Sorts are simpler: pick a property and a direction. Sorting by Due date, ascending, puts the most urgent item at the top. Sorting by Priority, descending, pushes your High items to the front.
Relations and rollups, in plain terms
A relation connects one database to another. Say you keep a Projects database and a Tasks database. In Tasks, add a Relation property pointing at Projects. Now each task can be linked to the project it belongs to, and opening a project shows you all of its tasks from the other side.
A rollup then pulls something through that connection and summarises it. On the Projects database, a rollup can count the related tasks, sum their estimated hours, or show the earliest due date. The relation is the link; the rollup is the calculation running across the link.
Two warnings. Build relations between two databases only — three-way webs get confusing quickly. And relations are not folders: nothing is moved or copied, the records simply point at each other.
Build your first database in ten minutes
- Create a new page, type /database and choose Table.
- Rename the title column to something specific: Book, Client, Task.
- Add three properties only — Status, Date, and one Select for a category.
- Type in five real records. Real ones, not "Placeholder One".
- Add a Board view and group it by Status.
- Go back to the table and add a filter: Status is not Complete.
- Use it for a week before you add anything else.
Keep it small, then grow
The temptation is to build a system for every corner of your life on the first afternoon. Resist it. One database you actually open beats five that look impressive and stay empty.
When you feel the pull to add something, ask what problem it solves. If the answer is "it would be nice", wait. If the answer is "I keep forgetting which invoices are unpaid", add the property, add the filter, and move on.
That is the whole trick with Notion databases: small, specific, and used.
Photo: DS stories / Pexels
