David Neira is an official Notion Ambassador and the founder of NotioStore, where he builds custom Notion operating systems for architecture, construction, and interior design firms. He run 40 Notion Setup Sessions per week and writes here about making Notion hold up under real client work.
You want a home page that shows your tasks due today, your active projects, and this week’s priorities, all at a glance. So you start copying: a table of tasks here, a list of projects there, and a week later you’ve got three copies of everything, half of them out of date, and no idea which one is real. You duplicated your data when all you actually wanted was to display it somewhere else. There’s a feature built for exactly that, and hardly anyone knows it by name.
The feature is the linked database view, and it’s the single most useful thing to learn for building dashboards. A linked view shows a database you already have on another page, filtered and sorted however that page needs, without copying anything. Master linked database views in Notion and you can surface exactly the right slice of your data anywhere in your workspace, all from one source of truth that never falls out of sync. It’s how every good Notion dashboard is actually built, and once you’ve made one, the whole idea of copying databases will feel like the mistake it was.
Duplicating a database feels like progress and creates a slow catastrophe. The moment you have two copies, you have two versions of the truth, and they start drifting apart immediately, a task marked done in one, still open in the other. Soon nobody knows which copy is current, so nobody trusts any of them, and the data you were trying to organize is now actively misleading you.
Then there’s the labor of keeping copies aligned, which is either constant manual updating or, more realistically, giving up and letting them rot. Either way, you lose. And because copying never actually gives you a live view of your real data, you can’t build a working dashboard this way at all, so you’re left navigating from page to page hunting for information instead of seeing it gathered in one place. The whole point of a connected workspace, one reliable source of truth, collapses the instant you start duplicating.
A linked database view solves this completely, and the idea is simple: it displays an existing database on a different page, without copying it. The data still lives in its one home database, but you can show it, or a filtered slice of it, anywhere else in your workspace. It’s the same database, just appearing in a new place.
Because it’s the same database and not a copy, everything stays in sync automatically. Edit a task in a linked view on your dashboard, and it changes in the source database and every other linked view too, because they’re all windows onto the same underlying data. You’re not making copies; you’re placing windows. That’s the mental shift: one database, displayed in many places, always current, on the same databases you already built.
And each window can be filtered and formatted for where it lives. The same Tasks database can appear as “due today” on your home page, “this project’s tasks” on a project page, and “everything overdue” on a team page, three linked views, three filters, one database beneath them all.
Step 1. Add the linked view. On any page, type /linked and choose “Linked view of database,” then pick the existing database you want to show. It appears on the page, displaying your real data. You’ve just placed a window onto a database that still lives elsewhere.
Step 2. Filter it for this context. A raw linked view shows everything, which isn’t the point. Add a filter so it shows only what belongs here, tasks due this week, this client’s projects, whatever the page is for. The filter is what turns a full database into the useful slice this particular page needs.
Step 3. Choose the right view type. A linked view can be a table, board, calendar, or timeline, independent of how the source database is displayed elsewhere. Pick whatever suits this spot, a calendar for deadlines, a board for status, so the same data shows up in the most useful shape for each place it appears.
Step 4. Repeat to build a dashboard. Add several linked views to one page, tasks due today, active projects, this week’s priorities, and you’ve built a dashboard: a single screen surfacing exactly what you need from across your whole workspace, every piece live and in sync. This is the payoff, and it’s just linked views stacked with purpose.
Here’s it working. An architecture studio wanted a team dashboard and built it the wrong way first, copying their projects and tasks into new tables on a dashboard page, which promptly drifted out of sync and became useless within days. Someone showed them linked views. They rebuilt the dashboard as linked views of their real databases, filtered to active projects, this week’s tasks, and anything overdue, and suddenly it was live: every update anywhere flowed straight to the dashboard, because nothing was copied. One source of truth, shown exactly where they needed it.
A linked view displays a database; it doesn’t create one. You need the source database to exist first, so build your databases, then surface them with linked views, not the other way around. Linked views are the display layer, not the data itself.
Each linked view also shows one database. A single linked view can’t merge two different databases into one combined view, so to show tasks and projects on the same dashboard, you add one linked view for each. That’s by design, but it catches people out who expect a single view to blend separate databases. And while you can filter and format each linked view independently, remember you’re always looking at the same underlying records, so an edit in a linked view is a real edit everywhere, which is the strength, but worth keeping in mind.
Finally, linked views show and filter data; they don’t summarize across databases or perform logic. For totals and counts pulled from connected records you still need rollups and relations, and for calculations, formulas. Keep dashboards focused, too, a page crammed with heavy linked views gets slow and cluttered, so show the vital few, not everything at once. Within those bounds, linked views are the feature that makes Notion feel like a dashboard tool instead of a filing cabinet.
Don’t plan a whole dashboard, just make one linked view. Open your home page, or make a fresh page, type /linked, and pick your tasks database. Then add a single filter so it shows only what’s due this week.
That one linked view, live, filtered, and perfectly in sync with your real tasks, is the entire concept in miniature, and making it once teaches you what no description can: you’re placing a window, not making a copy. From there, adding a few more to build a real dashboard is the same move repeated, and you’ll never duplicate a database again.
If you’d rather have a dashboard built to surface exactly what matters from across your workspace, linked views set up properly, live, and in sync, book a discovery call and we’ll build it with you.
A pile of tasks isn’t task management. Real task management is knowing, at any moment, what to do next, and that takes more than a list. This is a step-by-step tutorial for using Notion for task management.
Entrepreneurs can replace expensive tools with Notion by consolidating the overlapping ones, notes, docs, projects, wiki, simple CRM, into a single subscription, while keeping only the specialized tools that genuinely earn their price.
New to Notion? Discover the most common beginner mistakes and how to avoid them so you can build a smarter, simpler, and stress-free Notion system.
Built for the businesses that build everything else.
No product pitches. No padding. One weekly read for serious operators.