We have several Workspaces with exactly the same applications and automizations. Changes in the automization or the applications are therefore a hustle when rolling out a new feature or field. Working with a “master application” and a “master automization” could easily fix that problem.
Use case as following:
We have a ticket pooling system. Several “slave apps” in several Workspaces copy all the data into a master pool. Reason: Several clients that shall only see their entries, but we need the information on new entries in our master pool.
Simply updating the slave apps by adding a new button, a new field or a new automization causes immense workload on our side - since we need to change nearly 100 applications and automizations.
Working with a master application that changes all slave applications that have been associated with it (or created by it) would result in updating all applications in less than a minute. Same goes with automizations.