Skip to main content
Question

Viewing records from multiple boards in one board

  • November 4, 2025
  • 3 replies
  • 34 views

Forum|alt.badge.img+1

Our small creative team uses Airtable in a KanBan view to manage client workflow. Each client has a base. Within each base, we typically include the active teammate assigned to the task as a field on each record. This allows us to manage team bandwidth for that particular client, but we still have to manually manage our teams task assignments across various client bases.

Is there a way to pull records from different bases within a shared team workspace? We’d like to have an internal view stacked by team member.

3 replies

TheTimeSavingCo
Forum|alt.badge.img+31

If you’ve got a Business or above plan, you can use multi source syncing for this, it lets you grab records from multiple tables and put them into a single table, with 20 source tables being the max

https://support.airtable.com/docs/multi-source-syncing

---

If you don't have Business, this gets trickier.  The idea will be to have one base where you sync all the tables to (10 source tables max on Teams) and create one table to consolidate them all called ‘Consolidated’ or something.  The consolidation would consist of:

  1. 1 automation per synced table
    1. Trigger would be when a new record gets created in the synced table
    2. Action would be to create a new record in ‘Consolidated’ and link it to the triggering record
  2. In ‘Consolidated’ you would create lookup fields to grab the relevant data from each synced table (task name, date, which client etc)
    1. You’d end up with a ton of lookup fields, so e.g. if you have 10 source tables, you’d end up with 30 lookup fields if you only needed 3
  3. In ‘Consolidated’, create formula fields to consolidate the data from the previous step’s fields so that you can look at a single field see e.g. the date due

You could also try to create your own sync system by using Airtable’s Run a Script action in the source bases or use a third party automation tool

---

I take it there are business reasons why you can’t have all the tasks in one base instead?  Could you talk a bit about those?  The simplest way to handle this is really to have everything in one base, and if we can solve your reasons for having them in separate bases that might be easier if you don’t have a Business plan

 


Mike_AutomaticN
Forum|alt.badge.img+28

I guess you are keeping tasks in separate tables as your clients need to have access to that but you do not want to share all tasks (including internal and those for other clients with them)?

If that is the only reason, you could still handle everything under one unique base and only share different public (password protected) views with each client. Would this work?

Completely different matter, but would love to have you join our Airtable Hackathon! Make sure to sign up!!

Mike, Consultant @ Automatic Nation 
YouTube Channel


ScottWorld
Forum|alt.badge.img+35
  • Genius
  • 9788 replies
  • November 5, 2025

@CBo4Duckpin 

You can use syncing to collect your data from separate bases into one base, but there are limits on how many bases you can sync, so that won’t be a good long-term solution for you.

The best long- term solution for you would be to NOT split up all of your clients into separate bases, because that is not good database structure.

The ideal database structure is for you to keep all of your data in ONE UNIFIED BASE instead of separate bases.

This would enable you to unleash all the power of Airtable — automations, interfaces, dashboards, external integrations using tools like Make and Fillout — and will save you a ton of time that you might be spending by duplicating all of your database development efforts across multiple bases.

Hope this helps! If you have a budget and you’d like to hire the best Airtable consultant to help you with this or anything else that is Airtable-related, please feel free to contact me through my website: Airtable consultant — ScottWorld