1. What is the general goal of the feature?
ODK Central app users should be available across projects, so that we can mix and match sets of forms (organised as projects) to be available to different app users.
2. What are some example use cases for this feature?
Long term monitoring projects 1,2,3 each have a set of forms. The entire list of forms is too long and confusing for the ODK Collect users. However, we want to mix and match user access to projects so that we can show any combination of projects to any app user, and still configure multiple devices with one QR code.
App user 1 wants to see forms for project 1 and 3, but not for 2.
App user 2 wants to see forms for project 1 and 2, but not for 3.
ODK maintainer wants forms and their submissions in one place - otherwise we would solve this problem by duplicating forms on Central across projects.
The cardinality of model "app user" to model "project" should be a M2M instead of nesting the app user within the project model.
3. What can you contribute to making this feature a reality?
UAT along real world use cases. Not nodejs-savvy enough to work on backend.