Notion Database Guide 2026: Views, Relations, Rollups, Automations, and Synced Databases
Notion databases fail for most teams not because the feature is weak, but because the structure is wrong. Pages instead of records. Multi-select tags instead of relations. Manual summaries instead of rollups. Built correctly, a Notion database is an operational system. Built wrong, it is a prettier spreadsheet that still needs a human to keep it honest.
I implement work-management tools for a living (my firm, SSPM, is a Smartsheet partner), so I care less about Notion’s demo databases and more about what still works after month three. Everything below is checked against Notion’s help docs and pricing page on October 12, 2026.
The short answer
- Put anything you will filter, sort, assign, aggregate or automate into a database. Keep narrative docs as pages.
- Connect entities with relations, not tags. Aggregate with rollups. Compute on the page with formulas.
- Custom database automations need Plus or higher. Full Notion AI (Agent, Meeting Notes, Enterprise Search) is included on Business and Enterprise; Free and Plus get a limited trial.
- Synced databases from Jira, GitHub, Asana or GitLab are Business and Enterprise only, and they sync one way from the source into Notion.
Database vs page: the decision that saves you a rebuild
Pages are narrative containers: briefs, meeting notes, reference. Databases are structured records: projects, tasks, clients, content pieces. Notion’s UI makes them feel similar, which is why teams bury operational data in page trees.
If you will ever ask “show me everything owned by Sarah that is In review and due in two weeks,” you need database properties. If you will roll budget up from tasks to projects, you need relations. If a status change should notify Slack, you need a structured Status property, not a sentence in a page body.
Rule of thumb: operational data starts as a database. Context and writing stay as pages, often linked from a relation or a page property.
Views, properties and the shape of a useful database
A database is one set of records with many views. Table for editing, Board for status, Calendar for dates, Timeline for schedule, List for reading. Same data, no copies.
Useful properties early:
| Property | Use it for |
|---|---|
| Status or Select | Workflow stages |
| Person | Owner |
| Date | Due or launch |
| Relation | Link to Projects, Clients, or Tasks |
| Rollup | Count, sum or show a field from related pages |
| Formula | Derived fields on this page |
| Files & media | Specs and exports (watch Free’s 5 MB upload cap) |
Add properties when a filter or report needs them. Do not invent twenty selects on day one.
Relations and rollups (folding in the linked-database essentials)
A relation stores links to pages in another database (or the same one). Notion’s docs create them as one-way by default; turn on the corresponding relation in the destination database when edits should work both ways.
How to add one:
- Open the database, add a property, choose Relation.
- Pick the target database.
- Optionally limit the relation to 1 page (for example, one Order per Purchase).
- Toggle two-way if both databases need a matching property.
- Click into a cell and link the related pages.
A rollup sits on top of a relation. Add a Rollup property, pick the relation, pick the related property, then choose show original, count, sum, average and so on. If the rollup looks empty, the relation is usually wrong before the rollup settings are.
Self-relations work for dependencies (Task A blocked by Task B). Use one property for a simple bidirectional link, or two-way mode when you want separate “Blocked by” and “Blocking” fields.
Linked database views (Create linked view of this database) are different from relations: they are filtered views of the same database on another page. Use them for dashboards. Use relations when two different entity types need to connect.
For plan context and guest limits while you scale this architecture, see the Notion pricing guide.
Formulas and automations: what actually ships by plan
Notion formulas run on properties of the current page (and can use rollup results). Keep them readable. If a formula is doing heavy aggregation, push the aggregation into a rollup first.
Automations, per Notion’s help and pricing comparison:
- Free: Slack notification automations and buttons; you can use automations that come in templates, but you cannot edit full custom ones.
- Plus and above: custom database automations (property edited, page added, and so on) that set properties, create pages, and more.
Triggers can watch name, person, number, text, select and relation edits. Design Status changes as the spine of your workflow so automations stay simple.
Synced databases (external tools into Notion)
Synced databases pull Jira, GitHub, Asana or GitLab into Notion as a live, one-way database. Notion’s help center is explicit: the feature is available on Business and Enterprise, and changes must happen in the source tool to update Notion.
Two gotchas from Notion’s docs:
- If a source item is deleted, the synced row (and any Notion properties you added on it) goes away.
- If you add a Notion property whose name collides with a source property, that property will not sync.
Do not confuse synced databases with relations between your own Notion databases. Relations are available broadly; external sync is a Business+ feature.
When Notion databases are the wrong tool
- You need spreadsheet-grade joins, SQL and API-heavy ops: look at Airtable or a real warehouse.
- You need strict engineering workflows, sprints and Git-native issue tracking: Jira or Linear usually beat a Notion tasks database.
- Your “docs” are contracts and legal review cycles: Google Docs still wins on suggesting mode (see Notion vs Google Docs).
A practical starter architecture
For a delivery team, start with three databases:
- Clients (or Accounts)
- Projects related to Clients
- Tasks related to Projects
Roll up task counts and “next due date” onto Projects. Filter a Board view of Tasks by Owner. Put the narrative project brief as a page inside the Project record, not as a parallel page tree. That one pattern is what most “Notion isn’t working” teams were missing.
If you also publish with Notion, remember Sites have their own SEO limits; our Notion Sites guide covers custom domains and what Google actually indexes.
Common questions
How do I create a relation between two Notion databases?
Open the source database, add a property, choose Relation, pick the target database, then optionally enable the two-way relation so the destination database gets a matching property. Link pages from the relation cell.
What is the difference between a relation and a rollup?
A relation stores links to other pages. A rollup reads a property from those related pages and aggregates it (count, sum, show original, and so on). You need a relation before a rollup can work.
Are Notion synced databases available on Free or Plus?
No. Notion’s help center says synced databases (Jira, GitHub, Asana, GitLab) are available on Business and Enterprise plans, and they sync one way from the source into Notion.
Do I need Business for database automations?
Custom database automations start on Plus. Free can create Slack notification automations and use automations that ship inside templates. Full Notion AI features are included on Business and Enterprise.
Can Notion databases replace a CRM or Jira?
For a light internal CRM or a content pipeline, yes. For a sales CRM with forecasting, or for engineering issue tracking with Git workflows, a dedicated tool is usually safer. Notion is strongest as the system of record for knowledge and light operations around those tools.
Features and plan limits checked against Notion Help and notion.com/pricing on October 12, 2026. Notion changes plans often, so confirm before you buy.
Sponsored
