Is there a way to deny "anonymous editors" from being able to update existing features or create new features? I know this sounds strange, but I have a case where my organization is publishing some maps for public viewing, but we also using feature layers for Survey123.
I've come across a use case where after a user has signed on and downloaded the Form for Survey123 it is kept locally on the user's machine. The next time they open Survey123, they are not forced to log on. This person then becomes an anonymous editor. I don't want them to be able to update anything unless they have logged in, but I don't see this as an option in AGOL. I only see the options to do "
Since this issue came up while using Survey123, and I will cross-post a question there.