How to Build Notion Database With Multi-Workspace Cross-Linking

You want to link a database in one Notion workspace to a database in another workspace without duplicating data. Notion does not support direct cross-workspace database relations, but you can create a functional link using public pages, synced blocks, and manual references. This article explains three practical methods to achieve multi-workspace cross-linking between databases. You will learn how to set up each method, understand their limits, and avoid common mistakes.

What Multi-Workspace Cross-Linking Means in Notion

Notion stores all data inside a single workspace. A Relation property links two databases only if they exist in the same workspace. When you need to connect data across two separate workspaces, you cannot use the native Relation property. The workaround relies on Notion public pages, synced blocks, and manual URL references. None of these methods create a true two-way linked database. They replicate or reference data, and changes in one workspace do not automatically update the other unless you use a synced block. Understanding this limitation helps you choose the right approach for your use case.

Prerequisites

You need edit access to both workspaces. The source database must be published as a public page. The target workspace must allow pasting external URLs and using the Synced Block feature. You also need a Notion plan that supports public pages, which is available on all plans including Free.

Method 1: Publish a Database View and Link via URL Property

This method creates a clickable link inside a property of the target database. It is the simplest approach and works for any Notion plan.

1. Open the source database view
   Navigate to the database in workspace A. Create a view that shows the rows you want to reference. A table view with filters works best.
2. Publish the view as a public page
   Click Share in the top-right corner. Under Publish, click Publish. Copy the public URL that appears.
3. Add a URL property in the target database
   In workspace B, open the database where you want the link. Add a new property, select URL, and name it e.g. “Source DB Link”.
4. Paste the public URL into the property
   For each row that needs a cross-workspace reference, paste the public URL into the URL property field. Notion will display it as a clickable link.
5. Test the link
   Click the URL in the property. It opens the public page in a browser. The link always shows the latest data from the published view.

This method is read-only. You cannot edit the source database from the target workspace. If you update the source database, the public page updates automatically, but the URL property in workspace B does not change.

Method 2: Embed a Live View Using a Synced Block

Synced blocks allow you to paste a public Notion page link and display its content as a live embedded block. Changes in the source appear in the target within seconds.

1. Publish the source database view
   In workspace A, go to the database view you want to share. Click Share > Publish > Publish. Copy the public URL.
2. Go to the target page in workspace B
   Open the page where you want the embedded database to appear. Place your cursor at the desired location.
3. Paste the public URL as a synced block
   Press Ctrl+V on Windows or Cmd+V on Mac. Notion will prompt you to paste as a synced block or a link. Select “Paste as synced block”. The public view appears as a live embedded block.
4. Adjust the view
   You can resize the block by dragging its edges. The block shows the same view you published. Any filter or sort changes in the source update the embedded block.
5. Update the source to refresh the embed
   Changes to the source database rows appear in the embedded block within a few seconds. The embed is read-only; you cannot edit the source from workspace B.

The synced block method is ideal for dashboards or reference pages where you need a live snapshot of data from another workspace. It does not support editing or two-way sync.

Method 3: Manual Reference with Rollup Across Workspaces

This method combines a text property with a rollup to pull specific field values from a source database row into a target database row. It requires manual maintenance.

1. Create a public page for each source row
   In workspace A, open the database. For each row you want to reference, click the row to open its page. Click Share > Publish > Publish. Copy the public URL. Repeat for each row.
2. Add a text property in the target database
   In workspace B, add a new text property named “Source Row Link”. Paste the public URL of the corresponding source row into this property.
3. Create a rollup property to pull a field
   Add a Rollup property in the target database. Set the relation to a dummy relation within the same workspace (since cross-workspace relations are not possible). This step is a workaround: create a temporary relation to a single-row database that holds the source URL. The rollup will not pull data automatically; you must manually copy the field value from the source row and paste it into a text property in the target row.
4. Manually update the field value
   When the source row changes, copy the updated value from the source public page and paste it into the corresponding text property in the target database. This is a manual sync step.
5. Use the rollup to display the value
   The rollup property can display the manually entered text value. This gives you a field in the target database that shows a value from the source workspace, but it requires manual updates.

This method is labor-intensive and prone to data staleness. Use it only when you need to display a small number of specific fields across workspaces and you can commit to regular manual updates.

Common Pitfalls and Limitations of Cross-Workspace Linking

Public Page Security

Anyone with the public URL can view the published page. If your data is sensitive, do not use this method. Notion does not support password protection for public pages. Use workspace-level sharing with guest accounts instead if you need controlled access.

Synced Block Breaks After Page Move

If you move the source database to a different workspace or delete the published view, the synced block in workspace B will show an error. Always keep the source published view active and in the same workspace.

No Two-Way Sync

None of the methods above allow editing the source database from the target workspace. If you need bidirectional editing, consider moving both databases into one workspace and using a native Relation property. Cross-workspace editing is not supported by Notion as of 2025.

Rollup Values Become Stale

The manual reference method requires you to update values by hand. If you forget to update, the target database shows outdated information. Set a recurring reminder to check and refresh the values.

Method	Live Updates	Editable	Best For
Public URL in URL property	Yes	No	Quick reference links
Synced block embed	Yes	No	Live dashboards and reports
Manual reference with rollup	No	No	Small data sets with manual sync

You can now link databases across two Notion workspaces using public URLs, synced blocks, or manual rollups. Start with the synced block method for a live embedded view. For a simple clickable link, use the URL property approach. If you need to display specific field values, prepare to update them manually. To avoid stale data, set a weekly calendar reminder in Notion to verify that the cross-workspace references still point to the correct source rows.