Survey 123 Requires Publishing Permission

[TessaS]

We have a number of non-GIS staff that would like access to creating and editing Survey123 forms. Unfortunately that requires giving them publishing permission which is a privilege that could be abused unknowingly if staff aren't trained. 

I don't want to give publishing permission to non-GIS staff as I worry it will set a precedent that will result in us having to give even more people publishing permission.

Does anyone have ideas or solutions to this problem? 

[abureaux]

You looking for opinions?

Mine is to say "no". Spreading out development like that just never seems to work well in my experience.

In my case, I have everything centralized...

1. A few developers create S123 forms.
2. They send those forms to me for review.
3. I publish all forms through a single service account which owns all S123 forms and items.

If groups want a new form/process, they need to go through me. Work is then filtered down, as necessary. This then starts the process listed above.

Have had zero issues after standardizing everything. A few "pre-problems" have cropped up, but every time I investigate, they are found to already be resolved by the current process. E.g., A new security protocol is pushed by IT. Other groups have to fiddle with permissions, but mine is already in compliance just because of how data is structured.

[RyanUthoff]

I'll second this. No is a perfectly acceptable response, just be prepared for explanations on why you're saying no, AND providing them with an alternative solution (such as you gathering their requirements and building the survey yourself).

But, depending on your position at your organization, and before you start telling people no, consult with your supervisors and/or other stakeholders that could potentially override your decision. It's better that everyone is on the same page from the beginning rather than you start telling people no, just for your supervisor to override your decision.