We have recently set up a Survey123 form (using the web version) for one of our Viewer roles. We have gone down this route as they are able to edit their own submissions, with the correct settings (avoiding the need for them to be a Editor in any capacity). However, we have clear issues we have had to overcome when trying to achieve this;
1) As you need to set the form to Public for a Viewer to submit (this in itself needs changing urgently and I am aware of other comments/posts regarding this), I have worked around this by adding a field that checks the submitter's username. If it doesn't match an allow list of users set by myself (e.g. someone who is anonymous), then it will appear blank and not allow them to submit.
2) Because of this field I have added, it requires the form to recognise a logged in user which is clear by the options bar appearing at the top of the form with your name/username. However, with testing, the user accessing the form via our organisational content does not show this options bar and therefore does not reconise a signed in user.
With that being said, if the user logs into Survey123 directly (where they can then access the form and its related data) and proceed to open the link to the form itself after doing this then the options bar appears and shows them as being signed in, making the username check field operate correctly.
There are clear issues to overcome for Viewer lisences working with Survey123 as a whole but specifically there is a bug with users accessing forms via organisational content (I have mentioned Viewers here but this also applied to another Admin account we tested).
Has anyone else experienced this issue? How can this be raised as a bug with esri?
