Ticket - Manage Learner Enrollments

[SantiagoSuHe]

Description:

As an instructor, I want to manually enroll or unenroll learners in my course so that I can control participation, optionally send notifications, and ensure that users are properly registered.

Acceptance Criteria:

Enroll Learners:

1. Clicking the “Enroll Learners” button opens a modal titled “Enroll Learners”.
2. The modal contains:
   • A multiline text box labeled “Email addresses / Usernames”, where the instructor can input multiple entries separated by commas or line breaks.
   • Two checkboxes displayed below the input field:
     • Auto Enroll
       • If checked: users who are not yet registered will be automatically enrolled in the course.
       • If unchecked: users who are not yet registered will not be enrolled automatically, but will be allowed to self-enroll once they create an account.
     • Notify Users By Email
       • If checked: enrolled learners receive an email notification confirming their enrollment.
3. When clicking Submit, the system processes all valid users entered.
4. On success, display a confirmation message:
   • “Learners successfully enrolled.”
5. Users that fail to enroll (e.g., invalid email, already enrolled) are shown in an error message with details.
6. If no users are provided, disable the Submit button until at least one entry is detected.

Unenroll Learners:

1. Each learner row in the Actions column includes an “Unenroll” link.
2. Selecting Unenroll opens a confirmation modal with an Unenroll primary action button.
3. Clicking Unenroll removes the learner from the course and refreshes the table.
4. After success, display: “Learner successfully unenrolled.”
5. If the unenrollment fails, show: “Unable to unenroll learner. [add any necessary detail to improve the understanding of the different possible errors]”

Design: Figma

[diana-villalvazo-wgu]

Unknown: we should do async or sync tasks to enroll one or many learners? so probably if is async we will not know the outcome to show feedback message in the UI

[SantiagoSuHe]

@diana-villalvazo-wgu as we discuss in the today's call. For this card, we should keep the current background process as it is. There is this separate “nice-to-have” card for adding CSV upload functionality, and that feature is where asynchronous tasks and a “pending tasks” section would make more sense, since CSV files can include larger amounts of data. For now, we should continue using the existing approach.

[edschema]

Just a correction to the above conversation: CSV upload is nice to have for this tool (enrollments) as it would be a new feature for enrollments. For Cohorts, CSV is in scope as it is part of the current dash tool.
@diana-villalvazo-wgu @SantiagoSuHe