Survey123 Viewer License Cannot Submit Forms

JustinJohnston

I am working on an infrastructure project that we would like to solicit feedback on our design from construction contractors.  We need to keep our design information confidential.  I was hoping I could create a web app and Survey123 form and provide Viewer licenses to the contractors to allow the forms to remain confidential while allowing the contractors to submit feedback to us, but without edit privileges, they apparently cannot complete the form.  Unless I make the form public, they can't have edit privileges.  We cannot go purchasing $400 field worker licenses for a bunch of outside contractors to use once.  Does ESRI have a solution to this dilemma?  I saw complaints going back to 2002 asking for this to work, but it seems no change yet?  Anyone at ESRI care to shed light?  This seems counter intuitive that they would be able to see the form and not be able to submit it.

TylerGraham2

Viewer licenses are for viewing the data only, think like a manager's need to see data in a dashboard. You need a Mobile Worker or Creator License to submit data to non-public facing forms.  

When you mention the need to keep design info confidential, are you talking about the design of the form itself, or construction designs?  If it is the former, you're going to need to spend for the licenses. You'll want to review how many people/companies will be using the form at once and also your TOS for licenses and see if there is a way to consolidate the number of licenses you need to purchase.  e.g. it is very common for our consultants to purchase one mobile worker license for a project that may have 5-10 different people working on it.  The people don't work concurrently on the project, so the license is set up with a generic username/login and it is actually only being used by 1 person at a time. So, if your form isn't being by different contractors at once (like if it is a feedback form for an end of the project review) you might be able to find a way to reduce the number of accounts you need and not run afoul of esri. 

If it is construction design information, are they submitting a form with confidential info, or are they viewing confidential info?

If they are viewing confidential info, I would setup a "template" form and feature service to house the submissions. Each project/contractor would get their own specific form that dumps data into the existing feature service, and I would use a note field to include a link to a SharePoint site, or something similar, that houses the confidential data to review and would use its own (hopefully more reasonably priced) login credentials.   

If they are submitting confidential info, there is another option, but the people using the form can't go back and edit their submissions.  You would create a view layer of the feature service, have your form(s) submit to the view layer instead of the feature service.  Your view layer would be public facing and in the settings for the layer, you turn off Delete, Update, and for "What features can editors see?" you select "Editors can't see any features, even those they add." That should keep data from being seen in the public facing view layer, and you can use the feature service or other view layers to see the data internally.  I use this for one of our forms because we have a similar issue, maybe 30 people need to use the form, but these are on-calls and it might be from 3-10 people in a day submitting data.  There was no way I could come up with a justification to purchase 30 annual licenses that would only see sporadic use individually, and only for like 4 months of the year.  So, the form is public facing, but responses are hidden. That way if we get a bad actor, they can't see legitimate data to spoof it.  

You could even do a "password" in the form itself. Give the contractors a unique string that they enter in a text field and show/hide the rest of the survey based on them putting in the correct answer.