How to Build Notion Database Hub for Multi-Project Cross-Reference

Managing multiple projects in Notion often means jumping between separate databases. You lose track of which task belongs to which initiative. A database hub solves this by letting you cross-reference data from several project databases in one central view. This article explains how to build a hub using linked databases, relations, and rollups so you can see all your work in one place.

A database hub is a master database that pulls in data from other databases using relation properties. You can then filter and sort this combined view to show only what matters. This setup eliminates the need to duplicate work or switch between pages constantly.

By the end of this guide, you will have a functional hub that connects your project tasks, milestones, and resources. You will also learn how to avoid common mistakes like circular relations and broken rollups.

What a Notion Database Hub Does and What You Need Before Building It

A database hub is a central Notion database that aggregates records from multiple project databases. Each project database remains independent. The hub uses relation properties to create a many-to-many link between a hub record and records in each project database. For example, a hub record named “Q4 Marketing” can link to tasks in the “Campaign A” database and milestones in the “Campaign B” database.

Before you start building, you need the following:

• A Notion workspace with at least two project databases. Each database should have a consistent structure — for instance, all should have a “Status” and “Due Date” property.
• Editor or full access permissions to all databases you plan to connect. You cannot create relations to databases where you have only read access.
• A clear idea of what you want to cross-reference. Common examples include task status, assignee, priority, and deadline.

The hub database itself starts empty. You will populate it by creating relation links to existing project records. You can then use rollup properties to aggregate data, such as counting how many tasks in a project are marked “Done.”

How Relation and Rollup Properties Work Together

A relation property in a project database points to a record in the hub database. When you add a relation, Notion automatically creates a reciprocal relation in the hub database. This reciprocal relation shows all project records linked to that hub record. A rollup property then reads a property from those linked project records. For example, you can roll up the “Status” property from all linked tasks and display a summary like “3 Done, 2 In Progress.”

Steps to Build the Notion Database Hub

Follow these steps to create a hub that connects two or more project databases. The example uses two databases named “Marketing Tasks” and “Development Tasks.” Replace these with your own database names.

1. Create the hub database
   Create a new database in your workspace. Name it “Project Hub.” Add properties you want to organize by, such as “Quarter” or “Team.” Do not add relation properties yet. Keep the database empty for now.
2. Add a relation property to the first project database
   Open your first project database, for example “Marketing Tasks.” Click the + icon in the last column header to add a new property. Choose “Relation.” In the dialog, select “Project Hub” as the related database. Name the relation “Hub Link.” Notion will create a reciprocal relation in “Project Hub” named after your project database.
3. Add a relation property to the second project database
   Repeat step 2 for your second project database, “Development Tasks.” Use the same “Project Hub” database. Name this relation “Hub Link” as well. Now each project database has a relation pointing to the same hub.
4. Link project records to hub records
   In the “Marketing Tasks” database, open a task record. In the “Hub Link” property, click the empty field and select or create a hub record. For example, create a hub record named “Q4 Campaigns.” Repeat this for each task you want to cross-reference. Do the same in “Development Tasks.” Each hub record can link to multiple tasks across both databases.
5. Add linked database views to the hub page
   Navigate to the “Project Hub” database page. Type /linked and select “Linked database.” Choose “Marketing Tasks” from the list. Repeat to add a second linked view for “Development Tasks.” Now your hub page shows all tasks from both databases in separate views.
6. Create a master view with filters
   Add a third linked database view. This time, select “Project Hub” itself. In the view menu, click “Filter.” Add a filter: “Where Marketing Tasks is not empty OR Development Tasks is not empty.” This creates a combined view showing only hub records that have linked tasks.
7. Add rollup properties for cross-reference data
   In the “Project Hub” database, add a new property. Choose “Rollup.” Name it “Task Count.” Set the relation to the reciprocal relation from one project database, for example “Marketing Tasks.” Set the property to roll up to “Name” and change the calculation to “Count all.” This shows how many marketing tasks are linked to each hub record. Repeat for “Development Tasks.” You can also roll up “Status” using “Show original” to see a list of statuses.
8. Organize the hub layout
   Drag the rollup properties to the top of the database so they are visible in the table. Rename the linked database views to “Marketing” and “Development.” Group the master view by “Quarter” or another property if you added one.

After completing these steps, your hub database shows a summary of each project cluster. You can click a hub record to see all linked tasks from both project databases.

Common Mistakes and Things to Avoid When Building a Database Hub

Circular Relations Between Databases

If you create a relation from Project Hub back to a project database that already has a relation to Project Hub, you create a circular link. This does not break Notion, but it makes the database confusing. Only use the reciprocal relation automatically created by Notion. Do not manually add a relation in the hub database pointing to the same project database.

Rollup Property Returns No Data

A rollup property shows empty if the relation property it references has no linked records. Ensure that each hub record has at least one linked task in the relevant project database. Also verify that the rollup property is set to the correct relation and the correct property to roll up.

Linked Database View Shows All Records, Not Filtered Ones

A linked database view shows all records from the source database by default. To show only records linked to the current hub record, click the view menu and select “Filter.” Add a filter: “Where Hub Link contains [current page name].” This is a manual filter and must be set per view.

Duplicate Hub Records for the Same Project

If multiple team members create hub records independently, you may end up with duplicates. Use a naming convention like “Quarter_ProjectName” and enforce it with a template. You can also add a formula property that concatenates the quarter and project name to create a unique identifier.

Notion Database Hub vs Individual Project Databases: Use Case Comparison

Item	Database Hub	Individual Project Databases
Purpose	Cross-reference and aggregate data from multiple projects	Manage a single project in isolation
Data visibility	Shows all projects in one page with rollup summaries	Shows only that project’s data
Setup complexity	Requires relations and rollups; moderate effort	Minimal setup; create and populate immediately
Maintenance	Must maintain relation links when adding new records	No cross-database maintenance needed
Best for	Portfolio management, program oversight, cross-team reporting	Single team or project with no external dependencies

A database hub is not a replacement for individual project databases. It adds a layer of cross-reference on top of them. Use individual databases for day-to-day task management. Use the hub for weekly reviews and reporting.

You now have a working database hub that cross-references multiple projects. Start by linking your highest-priority tasks to a few hub records to test the setup. To take this further, add a formula property in the hub that calculates the percentage of completed tasks across all linked projects using the rollup values. This gives you a real-time health score for your portfolio without manual counting.