You want to link a database in one Notion workspace to a database in another workspace but the Relation property only works within the same workspace. Notion does not support direct cross-workspace Relation properties because the Relation feature relies on a single database ID that is unique to each workspace. This article explains why cross-workspace Relation properties are not available and provides practical workarounds using linked databases, multi-workspace setups, and third-party automation tools.
Key Takeaways: How to Link Data Across Notion Workspaces
- Relation property limitation: Relation properties only work within the same workspace because they reference internal database IDs that are not shared across workspaces.
- Linked database view: You can use the Linked Database view to sync an entire database from one workspace to another, then apply a Rollup property to simulate cross-workspace relations.
- Third-party automation: Tools like Zapier or Make can copy or update Relation data between workspaces by matching shared identifiers such as email or task IDs.
Why Notion Relation Properties Do Not Work Across Workspaces
The Relation property in Notion connects two databases by storing the unique ID of a page in one database as a reference in another. This ID is generated by Notion and is specific to the workspace where the database lives. When you try to create a Relation between databases in different workspaces, the second workspace cannot resolve the ID because it does not have access to the first workspace’s internal page index.
Notion also does not provide an official cross-workspace sync feature. Each workspace is a separate data silo with its own permissions, page hierarchy, and database schema. The Relation property is designed for linking data within a single workspace, not across workspace boundaries.
How Notion Stores Relation References
When you create a Relation between two databases in the same workspace, Notion stores a hidden property in each database that contains the page IDs of the related records. These IDs look like long strings of letters and numbers, for example: “abc123def456”. If you export a database, you can see these IDs in the CSV file. But if you import that CSV into a different workspace, the IDs no longer point to valid pages because the new workspace assigns its own IDs to every page.
What Cross-Workspace Sync Actually Means
Cross-workspace sync would require Notion to maintain a global ID system or a mapping table that translates IDs between workspaces. Notion does not offer this capability as of 2025. The only way to share data between workspaces is through the Linked Database feature, which duplicates the entire database view, not individual Relation links.
Workarounds for Cross-Workspace Relation-Like Behavior
Method 1: Use a Linked Database With a Rollup Property
This method is the closest you can get to a cross-workspace Relation without third-party tools. It works by creating a Linked Database view in your target workspace that mirrors the source database, then using a Rollup property to pull in a specific field from the linked database.
- Open the source database in Workspace A
Go to the database you want to link. Click the three-dot menu at the top-right corner of the database view. Select Copy link to view. This copies a shareable link to your clipboard. - Open Workspace B and create a Linked Database
In Workspace B, go to the page where you want the linked data to appear. Type /linked and select Linked database. Paste the link you copied from Workspace A. Notion will display a read-only copy of the source database inside Workspace B. - Add a Relation property in Workspace B
Now create a new database in Workspace B that will hold your local records. Add a Relation property to this local database that points to the Linked Database view. This Relation is fully functional within Workspace B because both databases are now in the same workspace. - Use a Rollup to pull data from the linked source
In the local database, add a Rollup property. Set the Relation to the one you just created. Then select a field from the linked database, such as “Task Name” or “Status”. The Rollup will display the value from the source database, giving the appearance of a cross-workspace Relation.
Method 2: Use Zapier or Make to Sync Relation Data
If you need to maintain two-way updates or more complex logic, use a third-party automation platform. This method requires a shared identifier between the two workspaces, such as an email address or a task ID that you manually define.
- Identify a shared key between the workspaces
In both databases, create a property that stores a unique value that will be the same across workspaces. For example, use a Text property named “Task ID” and enter the same value in both databases for records that should be linked. - Set up a Zapier trigger for Workspace A
In Zapier, create a new Zap. Choose Notion as the trigger app. Select New Database Item. Connect your Notion account for Workspace A. Select the source database. Test the trigger to confirm Zapier can read new items. - Add a Zapier action for Workspace B
Add a new step. Choose Notion as the action app. Select Update Database Item. Connect your Notion account for Workspace B. Select the target database. Map the shared key from Workspace A to the corresponding property in Workspace B. Then map any other fields you want to sync, such as status or date. - Enable the Zap and test
Turn on the Zap. Create a new record in Workspace A with a matching shared key in Workspace B. Zapier will update the record in Workspace B with the new data. This does not create a Relation property, but it keeps the data in sync so you can manually link records or use a formula to reference the shared key.
Method 3: Use a Central Database in a Shared Workspace
If you control both workspaces, consider moving the shared database into a third workspace that both teams can access. This is the most reliable approach because it keeps all Relation properties within a single workspace.
- Create a new workspace for shared data
Sign up for a new Notion account or use an existing one. Create a workspace named something like “Shared Operations”. Invite members from both original workspaces as guests or members. - Move the database to the shared workspace
In Workspace A, open the database. Click the three-dot menu. Select Move to. Choose the new shared workspace. Notion will ask if you want to keep a link in the original workspace. Select Keep a link so users in Workspace A can still access the database. - Create Relation properties in the shared workspace
Now that all databases are in the same workspace, you can create Relation properties between them. Open the database you moved and add a Relation to any other database in the shared workspace. This Relation will work normally.
If the Workarounds Do Not Produce Expected Results
Linked Database Shows “No Access” Error
This error appears when the source database link requires permissions that the target workspace does not have. To fix this, open the source database in Workspace A. Click Share at the top-right. Under Share to web, toggle Share to web on. Then copy the new shareable link and use it in Workspace B. Note that sharing to web makes the database publicly accessible to anyone with the link.
Rollup Property Returns Blank Values
A blank Rollup usually means the Relation is not correctly set up between the local database and the Linked Database view. Verify that the Relation property in Workspace B points to the Linked Database view, not to a different database. Also confirm that the source records in the Linked Database view have values in the field you are trying to roll up.
Zapier Does Not Update Records in Workspace B
This often happens because the shared key values do not match exactly. Check for trailing spaces, inconsistent capitalization, or hidden characters. In Zapier, use the Formatter step to trim whitespace and convert text to lowercase before the update action. Also confirm that the Zapier connection to Workspace B uses the correct Notion account.
Notion Relation Property: In-Workspace vs Cross-Workspace Workarounds Compared
| Item | Native Relation (Same Workspace) | Linked Database + Rollup | Third-Party Automation |
|---|---|---|---|
| Data freshness | Real-time | Near real-time (updates when page refreshes) | Depends on Zapier/Make polling interval |
| Two-way sync | Automatic | Read-only from source | Possible with two Zaps |
| Setup complexity | Simple | Moderate | High |
| Requires shared key | No | No | Yes |
| Works across workspaces | No | Yes (read-only) | Yes |
Notion does not support native Relation properties across workspaces. The workarounds described above let you link data between workspaces using Linked Database views, Rollup properties, or third-party automation tools. For the most reliable results, move shared databases into a single workspace where Relation properties work normally. If you need real-time two-way sync, consider using a dedicated project management tool that offers cross-workspace linking.