Hello,

Data relation between workspaces depends on the software. Many tools allow it via linked workspaces, APIs, integrations, or export/import, but it's not always automatic and depends on the specific platform's features.

Best Regard,

Helen

Hmm, what’re you trying to do?  You can sync tables between bases in different workspaces if that helps, and so if you have a Tasks table in Base 1 in Workspace A, you could sync that into Base 2 in Workspace B?

Hey ​@cecilia zhang would you mind sharing some more detail on your current use case?

Please find some initial insights below.

1. You can sync tables
2. You cannot link records from different bases.
3. You cannot reference different bases (regardless of the workspace) on Aritable native automations.
4. You can use Zapier, Make, n8n, or other automation tool to achieve item 3 above. More on this tools here.

With additional info we can probably find a workaround (if needed) for your need.

Mike, Consultant @ Automatic Nation

for example, if i have 4 business units, and I want to share the contact base among this 4 units. do you recommend me putting all in one workspace?

Yeah, generally people just put all their bases into a single workspace.  That said, if your needs require you to keep each business unit’s data separate from each other, then separate workspaces would be the way to go

---

For the Contacts base thing, if you’ve got access to the Data Library this might be a good use case for it.  If not, just make it a shared view and sync it to each business unit’s base and you should be fine

Hey ​@cecilia zhang,

Some additional info below! 

If the 4 business units still correspond to the same “business” I would also assess having all of your data (for all of your business units) under one unique base -unless you have good reasons not to.

Good reasons not to:
- Data security/access
- Record count

Feel free to follow up with additional questions/info and we can find the best solution for you!

Mike, Consultant @ Automatic Nation