NEW Notion Updates: The Relation Property, Page Sections, and Formula To Visualize Related Notes

TL;DR

Create a relation property with a forward link (e.g., **concept**) and enable a backlink (e.g., **descriptions**) to automatically populate reverse connections.

Briefing Cornell Notes

Briefing

Notion’s updated **Relation** property now supports a smoother, more navigable “hierarchy” between pages—especially when paired with **backlinks**, **page sections**, and a small **formula** that turns related counts into readable signals. The practical payoff: instead of digging through linked pages manually, users can jump between connected notes instantly and surface useful context (like how many related items exist) right inside a page.

The walkthrough builds a pizza-themed example using a single database (“All my notes”). Each pizza page links to other pages through a relation split into two roles: a forward link called **concept** and a backlink called **descriptions**. After creating the relation property, the backlink automatically populates so that when a user opens “pizza dough,” the page shows that its **concept** is “pizza,” and the “pizza” page can list all connected description pages. With side panel navigation enabled, clicking related links opens them in **Side Peak** (side view), and the same navigation behavior applies to relation links—making cross-page movement feel like browsing rather than searching.

The next step turns those connections into a dashboard-like layout. On the “pizza” page, the **descriptions** relation is displayed as a **page section**. Within that section, users can customize which properties appear for each related page—such as a **short explanation**—and even edit that text through the relation. To quantify the relationship, the guide adds a roll-up property named **number descriptions** that counts related description pages. Because roll-ups are numeric, a **formula property** called **signal** converts the count into a readable text indicator: if the roll-up count is greater than zero, the formula formats the number followed by the word “descriptions,” otherwise it returns an empty value. The result is a compact status cue that updates automatically as the database grows.

Several additional use cases show the same pattern working beyond pizza notes. In a family tree setup, a person page links to a **sources** database via relations, with a backlink back to **members**. The layout can switch between minimal relation display and richer **page section** views, and relations can include properties like **URL**, **gender**, **born year**, and even a **place of birth** relation that lets users jump directly to location pages.

A formulas hub demonstrates that relations can connect to other databases for both **functions** and **related formulas**, with formatting differences like inline code for syntax. The guide also notes that when a backlink isn’t explicitly created, Notion can still generate backlink behavior automatically through the relation.

Finally, the walkthrough uses the relation structure to create multiple database views that act like filters for hierarchical states. One view (“top tier”) surfaces notes where **concept is empty** but **descriptions is not empty**; another (“orphans”) isolates pages where **concept is empty** and **descriptions is empty**. The overall message is that the relation update—combined with roll-ups, formulas, and page sections—makes Notion databases far easier to navigate as they scale, turning linked notes into an organized, browsable system rather than a tangle of links.

Cornell Notes

Notion’s upgraded **Relation** property becomes most useful when it’s paired with **backlinks**, **page sections**, and a **roll-up + formula** that summarizes related pages. The pizza example connects pages through a forward relation (“concept”) and a backlink (“descriptions”), letting users navigate between connected notes quickly—especially with Side Peak enabled. Displaying the backlink as a page section allows users to show related properties like short explanations and edit them in context. A roll-up counts related pages, and a formula turns that count into a readable “signal” (e.g., “5 descriptions”) that updates automatically. The same approach scales to family trees, formulas libraries, and filtered database views for “top tier” and “orphan” notes.

How do backlinks and relations work together in the pizza example?

A single database (“All my notes”) contains pages like “pizza,” “pizza dough,” “pizza sauce,” and “pizza toppings.” The guide creates a relation property named **concept** that links from description pages back to the concept page. It also enables a backlink so that each concept page automatically shows its related description pages under **descriptions**. As a result, opening “pizza dough” shows that its **concept** is “pizza,” while opening “pizza” reveals all pages linked as **descriptions**.

Why display a relation as a page section instead of leaving it as a simple relation list?

Showing **descriptions** as a **page section** turns the related pages into a structured block within the parent page. That section can be customized to show specific properties from each related page (for example, a **short explanation**). It also supports editing related text directly through the relation, making the parent page feel like a curated view of its linked children rather than a set of links.

How does the roll-up count become a readable indicator using a formula?

The guide adds a roll-up property called **number descriptions** that counts the related pages connected through the **descriptions** relation. Since roll-ups produce a number, a formula property called **signal** checks whether that count is greater than zero. If it is, the formula formats the number as text and appends “descriptions”; otherwise it returns an empty value. This creates an automatic status cue on the page.

What changes when the relation is shown as minimal vs page section in the family tree example?

In the family tree setup, relations can be displayed in different layouts. A minimal view shows a compact indicator (e.g., a small symbol stating there is one related item such as “Brennan”). Switching to **page section** provides a richer, expandable layout where multiple related properties (like gender, born year, and place of birth) can be presented and navigated more directly.

How can filtered database views use relation emptiness to organize hierarchy?

The walkthrough creates views based on whether relation fields are empty or not. For “top tier,” it filters for pages where **concept is empty** but **descriptions is not empty**—placing “pizza” at the top. For “orphans,” it filters for pages where **concept is empty** and **descriptions is empty**—isolating pages like “tacos.” This turns relation structure into a practical navigation map.

What’s the significance of not creating a backlink in the formulas hub example?

In the formulas hub, relations connect to other databases for **functions** and to related formulas. The guide notes that when a backlink isn’t explicitly created for a relation, Notion can still generate backlink behavior automatically within the same relation, allowing users to navigate back and forth between connected pages without manually setting up the reverse link.

Review Questions

In the pizza model, what specific combination of relation roles (forward link vs backlink) makes the concept page automatically list its descriptions?
How do roll-ups and formulas work together to produce a human-readable “signal” from a numeric count?
What filter logic distinguishes “top tier” notes from “orphan” notes using relation emptiness?

Key Points

1
Create a relation property with a forward link (e.g., **concept**) and enable a backlink (e.g., **descriptions**) to automatically populate reverse connections.
2
Use **Side Peak** so relation links open in a side view, making navigation between related pages faster.
3
Render a relation as a **page section** to display and edit key properties (like **short explanation**) for each related page in context.
4
Count related pages with a **roll-up** (e.g., **number descriptions**) and convert that count into a readable status using a **formula** (the **signal** property).
5
Apply the same relation pattern to other domains (family trees, formulas libraries) by swapping the connected databases and displayed properties.
6
Build multiple database views by filtering on whether relation fields are **empty** or **not empty** to surface hierarchical levels like “top tier” and “orphans.”

Highlights

A backlink turns one relation into a two-way navigation system: concept pages automatically list their related description pages.

A roll-up count plus a formula can produce an always-updating text cue like “5 descriptions,” eliminating manual checking.

Displaying relations as page sections turns linked pages into a structured, editable dashboard inside the parent page.

Filtered views based on relation emptiness can classify pages into hierarchy tiers such as “top tier” and “orphans.”

Topics

Notion Relation Property
Backlinks
Page Sections
Roll-ups
Formulas