My guess is they have given up on this and expect us to deal with it through APIs or Flows. Look at it from their (commercial) perspective. Shared tables = less records = less revenue. Replicated tables = more records = more revenue (plus the APIs/Flows used to achieve it). Which would you pick with venture capitalists on your case?
I hope I’m just a jaded old man and am wrong …
Appreciate that @LeighBerre96926 and yes without hearing from the Knack team on why this appears to have been dropped we can only assume the commercial imperatives have driven the decision.
Especially given the enormous utility for shared tables being so strongly linked to the stated goals of Knack for no code/low code, reduction of the additional burden of repeated Flow or Make.com setups and the ever expanding use of resources and servers that are simply not needed with a simple solution.
I am of course stating again for anyone who might read this how important this waited for feature still is, and I think needs addressing by the Knack team to reassure us of it’s progress or otherwise.
@Kara or @Les can you please update us on this feature?
I do not know why to have a shared table between users of your app, when you can just add a select field for user (shared or private) , and add a filter to show shared data to from all users where everyone can access.I do not know if I am on the same page or talking about data sharing between apps.
Hi everyone – thanks for sharing your interest in Shared Tables. It’s clear this is a highly valuable feature for many of you.
Here’s where things stand:
• Q1 2025: We completed critical backend work to ensure all apps in an account are hosted in the same region. This was a necessary step to unlock both Flows and Shared Tables.
• Q2 2025: We’re focused on launching:
Next Gen Apps – major improvements to the Builder and Live App.
Custom Domains
2FA for Live App users
For Custom Domains and 2FA, we’re assessing whether they can be supported in both Classic and Next Gen Apps.
• Q3 2025: Shared Tables is being considered as a major feature focus. We’re seeing if we can get Data-layer permissions and Shared Tables delivered separately, or if we’ll need to have Data-layer permissions functionality in order to offer the Shared Tables functionality our users want.
We’ve heard the strong demand for Custom Domains, 2FA, and Shared Tables. As we’ve built out the new app framework, we’ve had to carefully sequence delivery — but this roadmap should give you a clear view of what’s ahead. Thanks for your continued feedback and support, please keep sharing thoughts and ideas!