Thanks for the feedback Kenn!
Instead of the proposed interface limited to 5 users, I’d personally love to see some sort of web spreadsheet for editing and adding users.
Yes - this was actually Allies team first idea after talking with your App Services team at Medic. The ability to have App Services, a technical partner or capacity built admin be able to add >100 of users via a CSV would be achieved by first downloading a template from the CHT which would include all the relevant columns. The admin would then fill it out offline and then upload it to the CHT, thus bulk creating >100 users at a time.
However, after further interviewing existing CHT admins, the bulk add idea featured in this forum post was the one that was found to be the most impactful. A tough choice, for sure!
What would the data look like in the contact docs that are created? For projects with contacts that have required attributes, this might cause data integrity issues. Can we add required attributes somehow? If not, will we be able to turn this feature off?
Great points! Indeed, the approach in this post is simplistic. It does not account for contact forms that have been extended to have required attributes outside of the 5 shown columns. This feature internally will use the new /api/v1/users API endpoint which actually has a small set of required fields. The net result would be users created with this feature may have data integrity issues.
We wanted to validate our assumption of this being impactful by making a Feature Release that partners could test. If not, and being able to turn it off and not having every possible field were blockers, then the Feature Release would either be improved to add features or not be iterated on further and deemed a failure.