Linking Pages in Notion: Break Data Silos with a Single Source of Truth

Linking Pages in Notion: Break Data Silos with a Single Source of Truth

The usual way teams track work is to write the same status, effort estimate, or deadline on multiple pages. When one page is edited, the others stay unchanged, so reports become inconsistent and the effort to keep everything in sync is huge.

The cost of duplicated data

Imagine a marketing team that records campaign performance on a “Results” page and also logs each task on a separate “Tasks” page. If a campaign’s spend changes, the team must manually update the related task entries, otherwise the summary numbers are wrong. This duplication creates two problems: extra manual work and the risk of contradictory information.

How Notion’s linked databases solve the problem

Notion lets you add a Relation property to any page. The relation ties that page to any other page in your workspace, creating a live connection. When the source page changes, every page that references it through the relation automatically reflects the update, establishing a single source of truth without copy‑paste or scripts.

To make the connection useful, you can add a Rollup property to a linked view. The rollup pulls a numeric or date field from the related pages and aggregates it (sum, average, min, max, or custom formula). This eliminates the need to manually roll up numbers across pages.

Worked example: a project tracker

Let’s build a simple project tracker using two pages.

1. Create a page called “Tasks”. Add a Title property and a Status select property (Not Started, In Progress, Done).
2. Add a Relation property named “Project”. Choose “Link to another page” and set the target to the “Projects” database (you can create a new database called “Projects” with a Name title). This creates a live link from each task to its parent project.
3. Open the “Projects” page and add a Rollup property called “Completed Tasks”. Set the relation to the “Tasks” database, choose the “Status” field, and select “Count” as the aggregation. The rollup now shows how many tasks in the project are marked Done.
4. On the “Tasks” page, edit a task’s Status to “Done”. Return to the “Projects” page; the “Completed Tasks” rollup updates instantly, reflecting the new count without any manual refresh.

Verification steps:

• After creating the relation, open the linked view on the “Projects” page. The task that you linked should appear as a row in the view, and its title will be clickable.
• Change the Status of a task on the “Tasks” page. The rollup count on the “Projects” page should change immediately. If it does not, check that the relation property is correctly set and that the view is set to refresh automatically (the default).

Trade‑offs and limitations

Linking pages is powerful, but over‑using relations can make the workspace feel crowded. Each relation adds a hidden connection that the UI must track, which can slow page loading when many pages reference many others. To keep performance healthy:

• Limit the number of relations a single page participates in; keep the most important links only.
• Use clear, descriptive names for relation properties (e.g., “Project” instead of “Link”).
• Periodically review the relation graph for circular references; a page that indirectly links back to itself can break the view.

Another limitation is the rollup rate limit. Very large databases (tens of thousands of rows) may experience delayed updates if many rollups calculate simultaneously. For most teams, this is not an issue, but if you notice lag, consider consolidating rollups or reducing the number of related pages.

Actionable closing

Start by identifying a piece of information that lives on multiple pages today. Add a Relation property on one of those pages, then create a linked view on the other page. Add a Rollup if you need aggregated numbers. Test the connection by changing a value on the source page and confirming the linked view updates instantly. By doing this, you turn scattered notes into a live, single source of truth, reduce duplicated effort, and keep your team’s metrics reliable.