If you have ever opened Notion, created a page, written some notes, and thought — “okay, but I could do this in Google Docs” — databases are the reason you are wrong.
Notion databases are what separate a fancy notes app from a genuine business operating system. They are the feature that lets a freelancer track every client, project, invoice, and deadline from one connected workspace. They are what lets a project manager run twelve simultaneous workstreams without a single spreadsheet. They are what makes Notion worth learning properly.
And yet — databases are also the feature most beginners avoid for too long, because they look complicated at first glance.
This guide changes that. We will cover every database type, every view, every property that matters, and the two most powerful concepts in all of Notion — Relations and Rollups — using real examples pulled directly from working templates. By the end, you will not just understand Notion databases. You will know how to build them.
Ready to start? Create your free Notion account here if you have not already.
What Is a Notion Database?
A Notion database is a collection of pages where every page shares the same set of structured properties. Think of it like a spreadsheet where every row is also a full document you can open, edit, and add anything to.
That last part is what makes Notion databases different from anything else. In a spreadsheet, a row is just data — cells with values. In a Notion database, every row is a page. Click on a task in your task database and you open a full Notion page where you can write meeting notes, embed files, add a sub-checklist, link to related items, and leave comments — while all the structured properties (Status, Due Date, Priority, Assignee) stay visible in the sidebar.
The combination of structured data and unstructured content in a single item is unique to Notion. It is why one database can serve as both a project tracker and a document hub at the same time.
The Three Things Every Database Has
Items — the individual entries. Each item is a page. In a task database, each task is an item. In a client database, each client is an item.
Properties — the structured fields every item shares. Title, Status, Due Date, Priority, Assignee. Each property has a type that controls what kind of data it accepts.
Views — the way the database is displayed. Table, Board, Calendar, Gallery, List, Timeline. The data does not change between views — only the presentation does.
Understand those three things and you understand the structure of every Notion database ever built.
How to Create a Database in Notion
There are two ways to create a database in Notion.
Full-page database — the database is its own page in your sidebar. Use this when the database is the main thing, not embedded inside something else. Examples: your master task list, your client database, your content calendar.
Inline database — the database lives inside another page. Use this when you want a database as one section of a larger page. Examples: a project tasks database embedded inside a project overview page, a budget table embedded inside a business plan document.
To create either one: type “/” on any Notion page and search for “Table,” “Board,” “Calendar,” “Gallery,” “List,” or “Timeline.” Notion will ask whether you want a full-page or inline database. Both are identical in functionality — the only difference is where they live.
The 6 Database Views Explained
Every database can have multiple views, and switching between them costs nothing — the data is identical in every view. Adding a second or third view to your database is one of the highest-leverage things you can do in Notion.
Table View
The default view. Looks like a spreadsheet — every item is a row, every property is a column. Best for databases where you need to see and compare many properties at once: client lists, inventory databases, budget trackers, content calendars with lots of metadata. Table view lets you freeze columns, reorder them by dragging, and hide properties you do not need — all without affecting other views.
Board View (Kanban)
Cards grouped into columns based on a Select property — usually Status. Drag a card from “In Progress” to “Done” and the Status property updates automatically across all views. Board view is Notion’s Trello equivalent, and for many workflows it is better: because each card is a full Notion page, clicking it opens detailed notes, sub-tasks, files, and comments. Best for: project task tracking, editorial pipelines, sales funnels, hiring pipelines, bug trackers.
Calendar View
Items placed on a calendar based on a Date property, displayed by month or week. Clicking a date creates a new item with that date pre-filled. Calendar view works best combined with filters — create a “Published” view filtered to Status = Published to see your historical record, and a “Scheduled” view filtered to Status = Scheduled to see what is coming up. Same database, two different lenses. Best for: content calendars, event planning, editorial schedules, booking systems.
Gallery View
Items displayed as visual cards with cover images. You can set the card cover to a page cover, a file/media property, or a specific image property. Best for: portfolio databases, product catalogs, recipe collections, template galleries, and any database where visual scanning matters more than data density.
List View
The most minimal view — items as a simple list with title and a small selection of visible properties. No visual weight, maximum density. Best for: reading lists, link databases, quick reference lists, and any database where you want fast scanning without visual noise. List view is also the fastest to load on mobile.
Timeline View
A Gantt-chart style view using a Date Range property (start date and end date). Items appear as horizontal bars spanning their duration. You can group by any property, zoom from days to years, and drag items to reschedule them. This is a feature that used to require expensive tools like Monday.com or Asana Premium — in Notion it is on the free plan. Best for: project roadmaps, sprint planning, campaign timelines, and any workflow where sequence and overlap between items matters.
Database Properties: The Complete Guide
Properties are the columns of your database — the structured fields every item shares. Choosing the right property types is the difference between a database that feels natural and one that fights you constantly.
Basic Property Types
Title — every database has exactly one Title property. It is always visible, cannot be deleted, and is the name of both the item and the page it opens.
Text — free-form text. Use for short notes, reference codes, or any field that does not fit a more structured type.
Number — numeric values with optional formatting: plain number, percentage, currency. Use for budgets, quantities, ratings, word counts, hours logged.
Select — a single dropdown value chosen from a list of colour-coded options you define. Use for Status (Not Started / In Progress / Done), Priority (High / Medium / Low), Category, Phase.
Multi-Select — same as Select but allows multiple values per item. Use for Tags, Skills, Platforms, Topics — anything where an item can belong to more than one category simultaneously.
Date — a single date or a date range with an optional time component and reminder. Use for Due Date, Publish Date, Start Date, Deadline, Contract Expiry.
Checkbox — a simple yes/no toggle. Useful as a quick completion flag alongside a Status select, or for binary fields like Invoiced, Reviewed, or Published.
URL — a text field that renders as a clickable link. Always use URL instead of Text for web addresses — it formats correctly and opens in a new tab.
Email and Phone — formatted contact fields that trigger the native email client or phone dialler on click. Essential for CRM and HR databases.
Files and Media — attach files, images, or videos directly to a database item. Use for contract PDFs, project briefs, invoice files, cover images.
Person — assign a workspace member to an item. Supports multiple people per item. Use for Assignee, Owner, Reviewer, Approver. Notion’s “Assigned to me” filter uses this property — indispensable for team databases.
Advanced Property Types
Relation — links items in one database to items in another. When you add a Relation property to Database A pointing to Database B, you can attach any item from B to any item in A. The relation is bidirectional — a backlink property automatically appears in Database B. This is the property that turns a collection of isolated databases into an interconnected system.
Rollup — calculates a value from a related database using a Relation property. Once two databases are linked, a Rollup lets you sum, count, average, min, max, or list values from the related items. Examples: count all tasks linked to a project, sum all invoice amounts linked to a client, average all ratings linked to a product.
Formula — calculates a value using other properties on the same item, like a spreadsheet formula. Use for progress percentages, days until a deadline, conditional logic, or concatenated text fields. Notion’s formula language is similar to Excel but considerably simpler to learn.
Relations and Rollups: The Most Powerful Concept in Notion
Most Notion tutorials explain Relations and Rollups with abstract examples. We are going to use a real one — taken directly from the database architecture inside the Project Management with AI template.
The template contains 30+ databases covering every phase of a project lifecycle: Discovery, Initiation, Planning, Execution and Monitoring, and Closure. Within that system, there is a Projects database and a Project Task Tracking database. Every task in the Task Tracking database has a Relation property called “Linked Project” that connects it back to a row in the Projects database.
In the Projects database, a Rollup property called “Task Count” counts how many tasks are linked to each project automatically. Another Rollup called “Completed Tasks” counts how many of those tasks have Status = Done. A Formula property then divides Completed Tasks by Task Count and multiplies by 100 to give an automatic percentage complete column — updated the instant any task is marked done, with no manual calculation whatsoever.
That is Relations and Rollups working as a chain. And the same pattern repeats across the entire template: the Risk Register rolls up to the project, the Budget database rolls up to the project, the Stakeholders database links back to the project. Open any single project record and you see the full picture — tasks, risks, budget, stakeholders, meeting notes — all connected, all live.
If you want to see Relations and Rollups in action across a fully built system, the Project Management with AI template is the clearest example we have built. It covers 30+ databases across five project phases — from business requirements and stakeholder mapping through to project closure and lessons learned — all connected through a single Projects hub database. It is built for professional project managers who want a serious Notion system without spending weeks building it from scratch.
A Real Relation Map: 9 Databases, 12 Connections
To show how far this scales, here is the complete relation structure from the Real Estate Investor Command Center template. Nine databases. Twelve bidirectional relations. Ten automatic rollups and formulas.
The central hub is the Deal Pipeline database. Every other database connects back to it: Properties (linking deal financial data to the physical address), Contacts (pulling the seller’s phone number through as a Rollup), Task Tracker (counting all action items for each deal), Marketing ROI (tracing which lead source generated the deal and powering a Cost Per Deal formula), Rehab Scope (all renovation line items visible on the deal), Ledger (all financial transactions with Total Expenses rolling up automatically), and Document Vault (contracts and reports linked to the deal with a Document Count Rollup).
There are also secondary connections: Rehab Scope connects to Contractors (each scope item assigned to a specific contractor), Contractors connects to the Ledger (every payment shows who received it with a Total Paid Rollup), and Properties connects to the Document Vault (inspection reports and title documents attached directly to the property record).
The practical result: open any deal record and you see the property details, seller contact info, every task, every expense, every document, and the marketing campaign that generated the lead — all on one page. Nine databases worth of information, accessible from a single record. That is what a properly built Notion database system looks like.
Database Filters: Smart Views That Update Automatically
Filters let you show only the database items that match specific criteria, and those filters update in real time as items change. Click the “Filter” button at the top of any database view and add conditions: show only items where Status = In Progress, where Due Date falls this week, where Assignee = current user, where Priority = High and Status is not Done.
The real power comes from combining multiple views with different filters on the same database. Here is a practical setup using a single task database:
- Today — Table view filtered to Due Date = Today and Status is not Done. Shows exactly what needs attention right now, every morning, automatically.
- This Week — Table view filtered to Due Date = this week. Your weekly planning view.
- Board — Board view grouped by Status. Your Kanban for drag-and-drop progress tracking.
- All Tasks — Table view with no filter. The complete master list.
Every view reads from the same database. Completing a task in the Board view removes it from the Today view automatically. Changing a due date in All Tasks repositions it in This Week view instantly. One database, four tools, zero duplication.
Database Templates: Pre-Fill Every New Item
Inside any database, you can create item templates — pre-built page structures that apply when a new item is created. Click the dropdown arrow next to the blue “New” button in any database, then select “New template.” Design the page exactly how you want every new item to look: add headings, checklists, callout blocks, even embedded sub-databases.
In a client database, a client onboarding template might include a Project Brief section with standard questions, an embedded task checklist for onboarding steps, a Meeting Notes section pre-formatted with date and agenda placeholders, and a callout block with the client’s contract link. Every new client gets the same structure in one click.
In a content database, a blog post template might include an SEO checklist toggle, a Research Notes section, a Draft section, and a Review Comments section. Every new post starts with this structure ready to fill in.
In a meetings database, a meeting minutes template includes Attendees, Agenda, Discussion Notes, Action Items as a to-do checklist, and Next Meeting Date. Every meeting entry is structured identically — making it easy to find information and generate summaries later.
The HR Management, Recruitment and Onboarding template uses database item templates extensively — every new employee record opens with a pre-built onboarding checklist, every new job opening populates with a standard screening criteria page, and every performance review starts from a structured template. It covers the full HR lifecycle: applicant tracking, employee database, leave management, training tracker, benefits manager, and performance reviews — all in one connected Notion system.
Linked Database Views: The Same Data, Everywhere
You can display a view of any database on any page without duplicating the data. Type “/linked view of database” on any Notion page, search for your database, choose a view, and it appears inline. Edit an item in the linked view and it updates in the original database instantly. The data is always the same — only the presentation is separate.
This is how power users build dashboards. A home dashboard page might contain a linked view of the task database filtered to Due Today, a linked view of the meetings database showing this week’s schedule, a linked view of the projects database showing active projects sorted by deadline, and a linked view of the finance database showing the current month’s expenses — all reading from four separate databases, all on one page, with no data duplicated anywhere.
Common Database Mistakes — and How to Fix Them
Building too many separate databases when one would do. New users often create a separate database for every context — Work Tasks, Personal Tasks, Side Project Tasks. The better approach: one Tasks database with an “Area” Select property. Filter and group by Area in different views instead of maintaining separate databases that can never talk to each other.
Using Text properties where Select would be better. If you are typing the same values repeatedly into a Text property — “High,” “Medium,” “Low” — that should be a Select property. Selects are filterable, sortable, colour-coded, and consistent. Text fields are none of those things.
Never adding a second view. Having a task database with only Table view is like having a filing cabinet where everything is loose in one drawer. Add a Board view for Kanban, a Calendar view for scheduling, a filtered Today view for daily focus. The same data becomes dramatically more useful with the right presentation for each context.
Adding Relations before understanding basic databases. Get comfortable with a single database first — properties, views, filters. Add Relations once you have two databases that genuinely need to share data. Complexity before necessity is the fastest way to build a system you abandon.
Forgetting database templates. If you spend five minutes setting up a new item from scratch every time, you need an item template. That five minutes multiplies across every new item you ever create. Item templates are one of Notion’s highest-return features and one of the least used.
Your First Database: A Step-by-Step Setup
Here is how to build a useful task database from scratch in under ten minutes.
Open a new Notion page. Type “/” and select “Table — Full Page.” Give the database a name: My Tasks. Notion creates a table with one property by default — Title. Add the following by clicking “+” at the top right of the table:
- Status — Select property. Options: Not Started (grey), In Progress (blue), Done (green), Blocked (red).
- Due Date — Date property. Enable the End Date toggle to optionally set a date range.
- Priority — Select property. Options: High (red), Medium (yellow), Low (grey).
- Area — Select property. Options: Work, Personal, Health, Finance — whatever fits your life.
- Notes — Text property. For quick reference notes visible in the table without opening the full page.
Now add a Board view grouped by Status for Kanban-style task management. Add a filtered Today view showing only tasks due today with Status not Done. Finally, create an item template with an Objective callout block, a Subtasks to-do checklist, and a Notes section. Save it. Every new task starts with that structure pre-built.
In ten minutes you have a task management system with three views, smart filtering, and a reusable item template. That is a database doing what a database is supposed to do.
Want a Pre-Built Database System?
If you want a professionally structured database system without building from scratch, the templates below have the entire architecture already configured — Relations, Rollups, views, filters, and item templates all set up and ready to use on day one.
The Project Management with AI template is the most comprehensive database system we have built — 30+ connected databases covering every project phase from discovery to closure, with AI-assisted meeting summaries, action item generation, and status reporting built in. Ideal for project managers and teams who need a serious Notion setup without starting from a blank page.
The Ecommerce Business Management System is built specifically for online sellers — order tracking, inventory management, product catalog, customer database, returns and refunds tracker, and financial performance monitoring, all inside one connected Notion workspace. Every database talks to the others, so you always have a complete picture of your store’s operations without switching between tools.
If you want to start with something free, the Everyday Life template is a great first database system — Everyday Tasks, Habit Tracker, Yearly Goals, Simple Budget, and Life Projects all connected through a Life Areas database. It is free to download and a perfect way to see how Relations and linked views work in practice before building your own.
Conclusion
Notion databases are the feature that transforms the app from a notes tool into a genuine workspace operating system. Once you understand items, properties, views, and the Relations and Rollups system, you can build connected data architectures that would require expensive SaaS tools to replicate anywhere else.
The path forward is straightforward: start with one database, get comfortable with views and filters, then add a second database and connect them with a Relation. From there, everything else is an extension of the same logic.
Get started with Notion free, grab the Everyday Life template as your first working database system, and come back for Post 3: how to build your perfect Notion workspace from scratch — dashboard, sidebar structure, and linked database system all covered.
Disclosure: This post contains affiliate links. If you sign up for Notion through my link, I may earn a small commission at no extra cost to you.
0 Comments