Notion Database Features Explained: Relations, Rollups, Formulas, and Views

Most Notion users stick to tables and checkboxes. This guide covers the features that actually change how you work: relations between databases, rollup aggregations, formula fields, and multi-view setups that let content teams run a full editorial pipeline without leaving Notion.

Notion databases are not spreadsheets with a nicer interface. They’re relational data stores with a query layer on top. Understanding that distinction is what separates users who outgrow Notion quickly from teams who use it to manage thousands of pieces of content efficiently.

Database Properties: What Each Type Does

Properties are the columns in your database. Choosing the right property type determines what you can filter, sort, calculate, and relate later.

The most useful property types for content work:

• Select / Multi-select — Status fields, category tags, author names. Use Select for single values (status), Multi-select where multiple values apply (topic tags).
• Date — Publish dates, review deadlines. Dates unlock calendar view and date-based formulas.
• Relation — Links rows in this database to rows in another database. The foundation of any multi-table content system.
• Rollup — Reads through a Relation property and aggregates values from the linked database (count, sum, earliest date, etc.).
• Formula — Computed values derived from other properties. More powerful than it looks.
• Files & Media — Featured images, attachments. Relevant if you’re tracking creative assets alongside content.

Relations: Connecting Databases

A Relation property creates a link between two databases. The most common content workflow use case: a Posts database and a Authors database, linked via a Relation property on Posts.

Once linked, each post row shows which author it belongs to. In the Authors database, a corresponding backlink shows all posts by that author.

Setting up a relation:

1. Open your database and add a new property.
2. Choose Relation as the property type.
3. Select the database to relate to.
4. Optionally enable the backlink so both databases show the connection.

Relations also work within the same database. A parent page relation lets you build hierarchies — useful for grouping blog posts under content pillars or campaign themes.

Content workflow example:

Three linked databases that power an editorial pipeline:

This structure lets you filter all posts by author, see all posts in a category, and roll up counts automatically — without duplicating data.

Rollups: Aggregating Across Relations

Once you have a Relation, you can add a Rollup property that reads through it. Rollups let you surface aggregated values from a linked database without leaving the current view.

What rollups can do: - Count the number of linked items (Count all) - Show the earliest or latest date from linked records - Sum or average a numeric field across all linked rows - Show all unique values from a linked property as a list

Practical example — tracking content volume by category:

In a Categories database with a backlink to Posts, add a Rollup property: - Relation: Posts (backlink) - Property to roll up: Title - Calculate: Count all

Now each category row shows exactly how many posts are assigned to it. Add another rollup on Publish Date (earliest/latest) to see when the category was last updated.

Formulas: Computed Properties

Formulas in Notion use a syntax similar to spreadsheet functions. They can reference any property on the same row.

Useful formulas for content databases:

Days since published (for freshness tracking):

dateBetween(now(), prop("Publish Date"), "days")

Status label with emoji:

if(prop("Status") == "Published", "✅ Live", if(prop("Status") == "In Review", "🔄 Review", "✏️ Draft"))

Estimated read time from word count:

format(floor(prop("Word Count") / 200)) + " min read"

Full author + title slug:

replaceAll(lower(prop("Title")), " ", "-")

Formulas update in real time as underlying properties change. A formula-based “days since last edit” column turns your database into a content freshness tracker without any manual work.

Views: Filtering and Displaying the Same Data Differently

Every Notion database can have multiple views each with its own filters, sorts, and display settings all reading from the same underlying data.

View types and when to use them:

Setting up a useful editorial board:

Add a Board view to your Posts database, grouped by the Status property. Create status options that match your actual workflow: Idea, Drafted, In Review, Scheduled, Published. Cards move across columns as status changes either manually or via a Zapier / Make automation that updates status when a step is completed.

Linked Databases: The Same Data in Multiple Places

A linked database is a view of an existing database embedded on another page, with its own filter and sort settings. The data is shared changes in one place update everywhere.

This is useful for surfacing a filtered subset of a large database on a project page, a team homepage, or a status dashboard without duplicating any records.

Create a linked database by typing /linked on any page and selecting the source database. Then apply filters (e.g., “Show only posts assigned to this project”) to scope the view.

Database templates define a default structure for new entries. For a blog database, a template might pre-populate:

• Status set to Draft
• A checklist of production steps (outline, draft, edit, SEO review, schedule)
• Placeholder headings in the page body (H2 sections you always use)
• Author relation set to the current user

Templates eliminate setup friction for recurring content types. A team running multiple content formats — long-form, case studies, changelog entries — can have a dedicated template per format so every new entry starts correctly structured.

To create a template: open the database, click the dropdown arrow next to New, then + New template.

Combining Features: A Complete Content System

These features compound. A mature content database for a Webflow blog might include:

1. Posts database — Title, Status, Publish Date, Author (Relation), Category (Relation), Word Count, Read Time (Formula), Days Since Published (Formula), Featured Image
2. Authors database — Name, Active, Post Count (Rollup from Posts)
3. Categories database — Name, Post Count (Rollup), Last Published (Rollup: max Publish Date)
4. Board view — Kanban by Status for the editorial pipeline
5. Calendar view — By Publish Date for scheduling visibility
6. Filtered table views — “My drafts” (filter: Author = me, Status = Draft), “Ready to publish” (Status = Scheduled)
7. Templates — One per content type with pre-filled structure

This system handles planning, production, scheduling, and performance tracking in one place — with the actual content living in the same page body as the database row.

If you’re publishing this content to Webflow, tools like Flozi can sync the Notion database properties directly to Webflow CMS fields, keeping metadata (publish date, author, category) in sync without manual copy-paste. See How to Build a Notion + Webflow Hybrid Content Workflow for the full setup.

Frequently Asked Questions

What’s the difference between a Relation and a Rollup?

A Relation creates a link between rows in two databases. A Rollup reads through that link and aggregates values from the linked database — count, sum, latest date, etc. You need a Relation before you can add a Rollup.

Can a database have multiple views with different filters?

Yes. Each view has independent filter and sort settings. A single Posts database can have a Board view for status tracking, a Calendar view for scheduling, and a filtered Table view per author — all from the same data.

How do formulas reference other properties?

Use prop("Property Name") to reference any property on the same row. Formulas can perform date math, string operations, conditional logic, and basic arithmetic. The Notion formula editor shows available functions and auto-completes property names.

What is a linked database?

A linked database is a view of an existing database embedded on a different page. It shares the underlying data but can have its own filters and display settings. Changes made in a linked database update the original, and vice versa.

Can I export a Notion database?

Yes. From the database’s ... menu, select Export to download as CSV (properties only) or Markdown + CSV (properties + page body content). You can also export your entire workspace from Settings → Export.

‍