Select to view content in your preferred language

Allow "Viewer" accounts to submit internal surveys

677
4
02-27-2025 05:20 AM
Status: Open
Labels (1)
Tiff
by
Frequent Contributor

My idea is to allow Viewer role accounts to submit to any and all Survey123 surveys when shared internally and shared with them.

Currently, public surveys are able to be filled out anonymously and without account licensing. If the survey is internal, it requires a mobile worker or editor account. Viewer accounts are not able to submit surveys internally.

This is counterintuitive that public surveys can be submitted by everyone, but internal surveys (that need to stay internal for security or privacy reasons) requires additional licensing roles. This is a big concern for us as we are assigning roles to hundreds of staff - for staff that mainly need to view information, but as a result require editor privileges, is not sustainable nor ideal long-term.

4 Comments
Tiff
by

NOTE: There is another idea posted with the same suggestion but for Enterprise with lots more kudos that you can also kudo below.

https://community.esri.com/t5/arcgis-survey123-ideas/allow-viewers-to-fill-in-and-submit-surveys-in/...

Tiff
by

Another update: As of yesterday I submitted a technical case to Esri support for this issue. There is an existing enhancement "In Review" ENH-00015140, which my case will add to. I will try to escalate and communicate these needs to Esri as best I can!

LindseyGreidanus

Thanks for submitting this idea, I just ran into this issue when I assumed an organization member could submit to an organization wide survey but they kept getting an error message. It didn't even occur to me until I found it on the forums that they wouldn't allow that. 

RoryKaip

To add onto this, we would like to use the GIS Request Management ArcGIS Solution and with Survey123 unable to have internal viewers submit surveys, it is essentially unusable for a large organization with many people requesting GIS work that have no need to edit. We are currently working on a workaround, but if the base functionality just worked, it would be much easier to deploy these Esri created solutions.