App Approval Process (be able to authenticate users, and be able to modify the form)
under review
N
Nick Mennecke
The form-based request workflow is far too limited. It is also made available to the public when it is enabled - which we don't want. So for now we have to keep using our other online form and work in two systems. To be useable, we would need the following features:
Ability to authenticate users, and capture their name, email, location, and title information, before a form could be submitted.
Ability to modify the form fields/questions for our needs.
K
Kate McDermott
under review
K
Kate McDermott
Nick Mennecke if we were to allow districts to have two versions of the list - a public version and an internal version - with separate links and information, and districts could turn on "app requests" only for the internal list... would we still need a way to authenticate users before they can request an app? or would the ability to have two lists that could be published/embedded in separate places (one publicly and one for staff only) solve that problem?