I wanted to start with this as a question, but it may be better as an "Idea".
Typically, we only want designated Editors interacting with our data. In unique cases, it is also possible to enable "Public Data Collection" on a Feature Layer and share this layer with the Public: then, anyone (in or out of the organization) can add new features.
What we're trying to achieve is an editable FeatureLayer for all members of our Organization (without handing out Editor roles to everyone). It seems possible to use a 'Public Data Collection' layer embedded in a JavaScript map/app, but that still leaves the editable feature service open to the public (no matter how obscure the URL and programming pattern might be, that still seems more exposed than limiting access through Portal configurations -- and it adds some overhead for simple apps).
If there's no straightforward method here, I'd propose that "Enabling Public Data Collection" on a feature service could function similarly with layers shared with the Organization.
