Link to other base


@Trent_Meekin I don’t believe linking between bases is available at any price level.


Hi there!
huge +1 to the feature. @Airtable_Support @Katherine_Duh - as for me this is a critical future to make healthy structure in any project.


@Airtable_Team @Katherine_Duh @Howie @Howie_Liu Please clue us in


+1 YES to all the comments above. This is a critical feature for airtable to really work for businesses. It is crazy to have to copy contact lists over to new bases for new projects/clients (particularly because we can not hide tabs within bases from editors, ie clients).

Also, we need this functionality from a timeline production standpoint. If you have several bases for several separate projects the calendar function is not nearly as powerful or helpful as it could be because a company can never visualize everything on their multiple calendars at once (without a lot of copying and pasting).

PLEASE give us an update @Patricia_Li @Douglas_Forster


Another +1 for linking bases. I scrolled through the whole post here and dont see a response from Airtable which I find very odd.


I just did the same thing: I read through every post for something from Airtable. It’s very frustrating: I can’t decide if I should dump Airtable for my company.


Adding my +1 for this feature – right now, the lack of this feature is making it tough to champion Airtable for our company. While I’m seeing teams adopting it for their own tables, what would make it SO powerful for us is the ability to link between our bases. Bases are owned by different teams within our company, and the ability to link and connect to each other’s bases would save SO much on work, duplication of efforts and allow each team to maintain their ownership while still getting the connections needed to work cross-functionally.

This is a must have for teams IMO. Everything cannot remain in one base to be effective when cross-functional teams are working together.


@Katherine_Duh @Andrew @Airtable_Team I’m adding my +1 as well - and the main thing really pushing me towards the need for discrete, but linked bases is your new blocks feature (which is amazing… amazing!).

Here’s a quick rundown of my use-case:

  • My company performs over 200 different test methods for the construction industry, and we participate in about 30 different proficiency sample testing programs covering some number of those test methods

  • I use Airtable to track our results on those proficiency samples, and used to keep them all in a single base, with a table holding all our test methods which were linked to the appropriate proficiency sample tables

  • Blocks made visual reporting of our historical ratings on proficiency sample tests an absolute joy; however, I had to create 3 bar graphs per proficiency sample table - one for each of our labs - to see each lab’s historical data for that sample type - that’s over 90 graphs, resulting in a Blocks dashboard that was entirely unwieldy

  • My solution - split each proficiency sample type into its own base - now I have a Blocks dashboard with only 3 graphs in each base; this is great, but now I have to copy my table of test methods into each of my 30+ bases, and update each one if we add a new test method to our repertoire, remove a method, or if a designation changes, or the method’s documentation changes, etc

Linked bases would allow me to have a single test methods base linked out to all my different proficiency sample bases to keep them all updated if one of our test methods changes. I would be entirely in favor of this being a “Pro” only feature.

And I agree with everyone else in the desire to at least hear something by way of an update from the Airtable team on their current thinking regarding this feature request.

Thank you, Airtable - much love, and blessings! :vulcan_salute:t2:


Another +1 for linking bases as a premium plan only option.

Ideally including look-up functionality if not roll-up.


It finally dawned on me:
To Airtable this topic is not about being challenged on the software side. This is about finances.

If your base reaches 1200 records, you need to upgrade to a paid membership.
By linking bases you can avoid this.
Also for pro users, when your base reaches 50k records.

Linking bases means: less income.


That would be true if the linking of bases were available to “Free” workspaces.

This is why so many of us commenting above have suggested, or else expressed consent with the idea that this should be a feature only available to “Pro” or “Enterprise” workspaces. This would preclude the possibility that Airtable would lose revenue due to this feature.

They have a team of developers who work hard to produce this software as a means of making a living to provide for their families, so I absolutely think they deserve the revenue from implementing a feature like this. I really do think it’s a software challenge for them, not a reluctance to lose revenue.


And I fully agree on that.

I do think that Airtable would be reluctant to make this available to pro users. It probably will be premium users only.


All of the above!

  1. Permission delegation, where a team can manage their own Base & Tables, but they link to a “Master" table/base which they can only read from. At the same time enabling to keep a single “normalized” copy of that “Master” data. One example is a “Customers” or “Contacts” table which is used by several teams in the company for different purposes in different bases and tables.
  2. I don’t see this as urgent, but I can see how someone may need to consolidate data from multiple tables.
  3. Even if you implement table and record level permissions and ways to hide/show Tables in a Base, it goes against all useful information navigation features you provide: Workspaces -> Bases -> Tables -> Records… Now I’m forced to pile all tables in a single Base and single Workspace if I need to link data. Navigation and Separation of information is important as you have more users and data… it makes easy to find what you’re looking for, what is the context of the data you’re looking at, etc.

Regarding permissions implementation. Today Base permissions can be [read, editor, commenter and creator] granted to a [specific user]. The change will require to extend permissions to target [everyone] with ANY permission on [Target Base]


@Airtable_Team @Airtable_Support talk to us please


I think this could also be solved by putting an organizational system internal to a base
all i have are tabs and a pretty poor popover. what i’d love would be a tree or folder system for grouping and navigating tables—then i actually prefer base being a boundary for linkage, as it makes me think clearly about the purpose of each base.

some utility other than copy and paste for moving tables between bases would then round out the solution, users would have a wonderful organization system for their organization system


@Airtable_Team ^ problem solved, holler @rosssclafani


Yesss!! I vote for this request as well!


Airtable, would be awesome if you can share your plans for this. :cricket::cricket::cricket:


I vote for this as well!


Another +1 for linking bases