Syncing multiple bases to a "Master" without records shared from one linked base to another

[Everrett_Thom]

Hi,

I am super new to this. Essentially I want to have a master base that my team and I can work from that is synced to 4 other bases that our partners work on individually. I don't want one partners data to reflect on another partners base. Is this possible?

TIA!

[Ron_Daniel]

Hi @Everrett_Thom ,

That is completely doable! However, it really depends on what each base is using the data for. 

For example, let's say your master base is Client Info. The partner bases would each have a Client Info table that is synced to the Client Info base. Your partners could do whatever they do, referencing all the clients and related information. However, they would not be able to edit any client info - changes to the client info would need to be made in the master base.

[ScottWorld]

@Everrett_Thom 

Due to the editing limitations that @Ron_Daniel mentioned above, it's unlikely that you would want to sync the data out to 4 different bases, unless you are on a business or enterprise plan, in which case you could turn on 2-way syncing.

The better option that you would probably want to do is to keep all of your data in one base, and then create an interface that is filtered to only show each partner their own data.

You would need to create ONE interface page, and filter that page to only show you the records where the user’s email address (or the user field) matches the currently logged-in user.

To do this, you will need to have either an “email” field or a “user” field filled in for each record. Then, you can filter by one of those 2 fields.

And you can use the “preview” button at the top of the screen to see how it would look from different users’ point of views.

Hope this helps! If you’d like to hire an expert Airtable consultant to help you with anything Airtable-related, please feel free to contact me through my website: Airtable consultant — ScottWorld 

[TheTimeSavingCo]

Yeap, it is.  If you've got a Business / Enterprise plan this is pretty straightforward with two way syncing, and you have the option to either:
1. Create one base per partner and then sync one view from each of those bases to a single table in your main base via multi-source syncing: https://support.airtable.com/docs/multi-source-syncing
2. Create a table in your main base and have one view per partner, then sync that view to each partner's base
  - You'll need to create a system to ensure that records created per partner don't show up in the other views

If you're on Teams, this becomes tricky as you can only sync one way, so either you can edit the data or your partners can edit the data, but not both.  Workarounds exist for this (e.g. using third party automation tools like Make, using third party form tools like Fillout), but they could get tedious to deal with depending on your workflows

If your partners are the ones that need to be able to edit the data, getting it to show up nicely in your main base would be troublesome as well as you don't have access to multi-source syncing, so you'd need to create automations to help you consolidate the data, then use formula fields to consolidate that data into fields

---

Is it that you want your partners to be able to create their own automations, tables, fields etc?  If you don't need them to do that then I reckon you could just use an Interface for this instead; might be cheaper too (depending on how many people are using it) if you use the new Portals functionality which bills at US$120 for 15 users: https://support.airtable.com/docs/es/using-airtable-portals-for-external-collaborators