Hey all,
Just spent multiple hours today with a client, albeit totally on me! But we were trying to allow users to create new linked records in a Public Form. Most of their users will be internal and executive staff who are logged in, but they have a subset of users, who need quick access to form creation while they’re working inside a hospital, so we don’t want them to have to log-in to submit the form.
Everything obviously way easier if they’re logged in, but since they’re not, we enabled the Public Form. Definitely my bad for not testing multiple times on the Public Form side of things after we got under way, but we ended up building out an amazing form and automations and logic that completely doesn’t work on a Public Form 
.
Would there be a way [inside build mode] to differentiate features that are available for internal form creation rather than Public views? Something similar to when a feature is only available on a higher paid plan it could say “internal form only” or something- instead of disabling the feature itself since some users may want the option to have a Public AND an internal form all on the same build.
Or a way to preview and test public forms inside build mode? As it is, I need to copy/paste the URL and open up a testing form- which does only take two seconds, but human habit keeps me in build mode to test because that “feels” faster. I’m first to admit we humans can be silly with our behavior!
TLDR: Could there be a way in build-mode for a builder to know that a feature isn’t available on a Public Form when they’re building a Form that has Public Form toggled on?