[Auth & ACLs] Introduce "public" surveys

[gino-m]

Public surveys can be "public" ("Anyone can contribute") or "unlisted" ("Anyone with a link or QR Code can contribute").

These surveys would be accessible to all pass-listed users provided they know the URL. They would not show up in survey list unless the user has previously access the survey.

This would unblock #1793 and #2020.

Qs:

• How do they get back into an unlisted survey if they no longer have the QR code or URL? Introduce @vittorino @lecrabe should we introduce a "recent surveys" section?
• Where is this option set and how? @vittorino

[gino-m]

In #2117 (comment) @jo-spek said:

TBH I don't know what exactly you mean with these distinctions (public listed / unlisted / survey templates). This is what I understand:

My understanding is that there at least three related CUJs we want to address here (@kenstershiro @lecrabe cmiiw):

1. [P0] When organizing trainings or campaigns, adding data collectors by email address is error prone and time consuming. Survey organizers want an easier way to provide access to an entire group of users.
2. [P1?] New users want to try out Ground for Android quickly, even if they haven't been invited to a survey yet.
3. [P1?] Survey organizers often surveys with similar data collection tasks, so they want to have a way to quickly add those common tasks.

Solutions:

• Anyone with QR Code can contribute (unlisted): Allowing organizers to share a survey by QR code (or maybe URL) would solve CUJ 1 - survey organizers would share the URL or QR code with data collectors, who would discover the survey using that artifact. The survey is not listed in the list of publicly available surveys, so only those with the link or QR code would be able to access the survey.
• Anyone can contribute (public): Allowing organizer to set a survey as "public" would allow everyone to contribute data to the survey as data collectors. This addresses CUJ 2 above - new users will automatically see these in their survey list after they download the app.
• Task templates: Allow survey organizers to save one or more tasks as a template. With the above solution the priority of this solution was bumped down, since it introduces additional complexity to the survey editor, and will require some careful thought from product and UX.

Does that make sense?

[gino-m]

@lecrabe @kenstershiro isn't this blocking trainings? If so may want to bump to P0?

[lecrabe]

Yes, let's bump to P0, not sure where to do that...

[kenstershiro]

Upped to P0, was already top of the list for @rfontanarosa and @vittorino - please shout if there are any questions on the detailed requirements. @jo-spek FYI