How to Use Notion Relation Property With Workspace-Wide Reference

You want to link a database entry to a record in a completely different database anywhere in your Notion workspace. The Notion Relation property connects rows across databases, but by default it only works within the same page hierarchy. Workspace-wide reference is a technique that lets a Relation span across any two databases, regardless of their location in the sidebar or inside nested pages. This article explains how to set up a workspace-wide Relation property, what prerequisites are needed, and which pitfalls to avoid.

How Notion Relation Property Works Across the Workspace

The Relation property in Notion lets you link a row in one database to a row in another database. When both databases are on the same page or in the same parent page, the Relation works seamlessly: you click the Relation cell and see all entries from the target database. For workspace-wide reference, the key requirement is that both databases are at the same hierarchical level. That means both should be top-level pages in the sidebar, or both should be sub-pages of the same parent page. If one database is nested three levels deep inside a page and the other is a top-level page, Notion will not show the second database in the Relation search list. The workaround involves using a Rollup property that pulls data through a Relation in a shared parent page.

Prerequisites for Workspace-Wide Relation

Before you begin, verify that both databases are visible in the sidebar. Open the sidebar and confirm that each database appears as a page. If a database is inside a page that is collapsed, expand that page so the database is listed. The Relation search tool in Notion can find any database that is a direct child of the current workspace or of a shared parent page. If you cannot see the target database in the Relation property picker, move the target database to a top-level position temporarily, create the Relation, then move it back.

Steps to Create a Workspace-Wide Relation Property

Follow these steps to link two databases that are both at the top level of your workspace or both inside the same parent page.

1. Open the source database
   Navigate to the database where you want to add the Relation property. This is the database whose rows will contain the linked reference.
2. Add a Relation column
   Click the + icon in the top-right corner of the database table view. From the property type list, select Relation. A new column appears.
3. Select the target database
   In the Relation configuration dialog, click the Select a database field. A search list opens showing all databases in the workspace that are at the same hierarchical level. Type the name of the target database and click it. Then click Create relation.
4. Choose a relation name
   Notion will prompt you to name the relation. By default it uses the name of the target database. You can change it to something descriptive like Linked Project or Customer Record. Click Create relation to finish.
5. Link rows between databases
   Click any cell in the new Relation column. A pop-up shows all rows from the target database. Select one or more rows to link them. The linked rows now appear in both databases as connected entries.

Using a Rollup to Bridge Different Hierarchies

If your databases are nested in different parent pages and cannot be moved, use a Rollup property to pull data across the hierarchy. This method requires a shared parent page that contains both databases as children.

1. Create a shared parent page
   Create a new top-level page in your workspace. Name it something like Data Bridge. Move both databases into this page as sub-pages. Now both databases are at the same hierarchical level inside Data Bridge.
2. Add a Relation between the databases
   Open the source database inside Data Bridge and add a Relation column. Select the target database (also inside Data Bridge) as the relation. Link the desired rows.
3. Add a Rollup property
   In the source database, add a new property and choose Rollup. For the Relation field, select the Relation you just created. For the Property field, select the column from the target database whose data you want to display (for example, Name or Email). Configure the Rollup aggregation as Show original or any other option.
4. Use the Rollup value as a workspace-wide reference
   The Rollup column now displays data from the target database, even if the source database is later moved outside the shared parent page. The Rollup retains the connection as long as the Relation property remains intact.

Common Mistakes and Limitations

Relation search does not show the target database

This happens when the target database is nested inside a different parent page than the source database. Move the target database to the same parent page as the source database, create the Relation, then move it back. The Relation will remain connected.

Linked rows disappear after moving a database

If you move a database to a different parent page after creating the Relation, the Relation may break. To prevent this, create a Rollup property before moving the database. The Rollup will preserve the reference even if the direct Relation becomes inaccessible.

Rollup shows empty values

An empty Rollup usually means the Relation property is not linked to any rows. Verify that the Relation column contains at least one linked entry. Also confirm that the Rollup property is referencing the correct Relation and the correct target property.

Cannot delete a database that has a Relation

Notion prevents deletion of a database that is used in a Relation property in another database. Remove all Relation properties that reference the database before deleting it. Open each connected database, click the Relation column header, select Edit property, and delete the Relation.

Item	Direct Relation (Same Hierarchy)	Rollup Bridge (Cross-Hierarchy)
Setup complexity	Low — add a Relation property and select the target	Medium — requires a shared parent page and two property types
Database location flexibility	Both databases must be at the same hierarchical level	Databases can be in different parts of the workspace after setup
Data displayed	Direct links to target rows	Values from a specific property in the target database
Risk of broken links after move	High — Relation may break if a database is moved	Low — Rollup retains the reference as long as the Relation exists

You now know how to set up a workspace-wide Relation property in Notion. Start by ensuring both databases are at the same hierarchical level. If they are not, use the Rollup bridge method to link data across different parent pages. As an advanced tip, create a dedicated Data Bridge page in your sidebar to host all cross-database Relations, then use Rollup properties in your working databases to pull the data you need.