I separate data into multiple bases for ease of use, and team-split.
However, I see Interfaces as a way to show data to the client (which could come from multiple bases).
I don’t like having to share multiple Interfaces.
Also, could Interfaces become a little bit as a customer login feature (as softr io allows)?
Just adding our use case and +1. We have bases split by project/department, with syncs set up where they interact, so the team only access the bases/data they need. But our comms team regularly use data points from all departments. An interface that spans bases could mean they only need one interface to refer to, rather than four/five.
Also, even on Enterprise - I've found that even with automations running an action regularly to keep the syncs/base active, the numbers are very frequently out of date. I was hoping to set up a monthly digest type email, but am currently doing it manually, as the automated emails (based on the one base of synced data from multiple bases) were never accurate...
Would love this feature as well to combine different segments of our teams' workflows into one master interface. Right now if we sync a table from base A to base B to get it into B's interface, the comments added in B's interface to the record in B obviously don't translate to the record in base A. Hard to capture conversations across teams without giving everyone multiple interfaces.