[feat] Bulk-Invite Users for an Assessment

[Sam-Runner]

Requesting a feature enhancement that enables the bulk-invite of users for a given Assessment. Since .xlsx can be messy, likely easiest to keep it simple with .csv templates. Providing two CSV examples that Microsoft uses for their Entra Bulk Operations, as inspiration to work from.

UserCreateTemplate.csv
UserInviteTemplate.csv

Suggested fields (Columns) would be:

• Email (required)
• Assessment ID (required)
• Assessment Group ID (Required)
• Assessment role (Optional; Defaults to "Participant"; Room to discuss if it should be numerical ID value or string literal)
• Firstname (Optional; Observed behavior is that Clerk with overwrite this once user signs in for first time)
• Lastname ((Optional; Observed behavior is that Clerk with overwrite this once user signs in for first time)

Would need to provide some basic "scaffolding" to help instruct the user how to find the assessment and group IDs to populate with. Checks are necessary so we know where to assign invited users.

Things to consider:

• Admin-only, or should Facilitators/Assessment Managers also have access? Just need to consider security checks to avoid a trivial attack where someone can assign users to an assessment they don't have access to.
• Need to consider testing and error handling for a user who tries to assign against any invalid ID, or tries to assign to a Assessment Group ID that belongs to a different Assessment than the one a user is being assigned to.
• How will this handle adding users who've already enrolled in the system? We don't want to overwrite user-entered details (I.E: First and last name) for an existing EMPACT user whose email gets added to participate in a new assessment.
• CSVs can be janky and buggy, especially if we're handing over a user template for them to modify. Need to consider failure modes and error recovery if someone manually tries editing the CSV template and the provided data no longer aligns, or is nonsensical in context. Default assumption is that safest option is to warn user there was an error, highlight where the parsing error occurred, and abort the entire import, as misaligned data could leave a mess if we try to interpret/recover on their behalf.
• In that vein: Seems worth having a preview screen we present to the user demonstrating "What-if" they completed the CSV upload, before we let them "Confirm" the operation.