@Jordan_Scott1 Hello. Seems we have the same questions here.
1/ Are you sure that when you publish a base in Universe, that it will also include the interfaces for users outside our organisation that would copy that base?
2/ Talking about contest, we would also much like to submit a full use case that solves a problem. Currently an Interface just using the available elements is quite limited and we also use automations to show the full potential of using interfaces. We see an interface as being like a final product/solution where a user should not even need to go into the base or tables, so if the contest is to create some interfaces that just use the available elements, it really limits the creativity and even more the "functional & actionable (25%) criteria in the judging criteria.
@Jordan_Scott1 Glad to hear it! Is there anything in particular we need to do when publishing to the Universe to ensure that the Automations carry over? Currently, if I publish to the Universe and copy the base, automations do NOT travel with it. Is there something I’m doing wrong when publishing?
This is not my experience. I published a base and tried using it. While the new copy of the base from the universe has the interface, there are no automations. When I make a public share link and enable copying of the base, the copied version also has the interface but no automations. This is different from when I duplicate a base. If I simply duplicate the base, I get both the interface and the automations and simply have to turn the automations on.
I’m 99% sure that automations do not carry over into the universe. I also, like @kuovonne, created a second account to test this. I used the base template I had put up in the Universe with my primary account as my contest entry, and it did not contain automations.
What I ended up doing is creating a table where I created a record for each of the automations my Interface relies on, and writing a description of how it works and what it does, and attaching screenshots of the automation setup.
Hello! Also now 99.9% sure that automations are NOT carried over. I just wanted to make sure and have just published a base that contains interfaces, extensions and automations in Universe. Extensions & Interfaces are there when I copy the base with a new user I created for testing purpose. Automations are just NOT there…
The only way I know to share automations is the following: > creating a base containing the automations and then allowing users to access and then Duplicate the base. If the base is duplicated, then the automations will be duplicated along with it.
The problem with that method is that
1/ it’s not published and public
2/ if you share that link with a user that is not a registered airtable user, there’s a huge risk that that user will become your “co-worker” instead of having him using your base and automations on his own.
@Jordan_Scott1 it would be great if you could double check and if, like you said previously, the automations should carry over, explain if there is a way to do that within the Universe? Thanks a lot
Thank you all for your patience ad we looked into this as it’s not expected behavior. In the meantime, if you are using automations for your interface, or would rather not share on universe, please create a base invite link and use that URL for your submission instead. This link will only be shared with the Airtable team and will not incur any additional charges to your account.
@Jordan_Scott1 Thank you so much for giving us resolution on this issue.
What sort of permissions do we need to include with the base invite link? Are read-only permissions okay, in case the link gets leaked to someone outside of Airtable, or if we want to share the base with other non-Airtable people? Will Airtable be duplicating the base and turning on the automations?