Blackboard roster desk for registrars and coordinators

Build me an internal roster desk that my registrar team and program coordinators work out of instead of clicking through Blackboard admin screens all day. It has three tabs: Student lookup, Course roster, and Bulk enroll. Nothing runs on a schedule, this is a staffed desk people open and work in.

A course picker in the header drives the whole app. Load the list of terms with the Blackboard Get Terms operation and let the coordinator choose one, then list the sections for that term with Get Courses filtered to the selected term, so people land on the courses they own instead of scrolling the whole catalog. Remember each user's last selected term and course between visits.

Student lookup tab: search by name, username or email with Get Users and show the matches in a result list. When one is selected, load the full profile with Get User and every course they are enrolled in with Get User Memberships. Show one row per course with the course name, the section, their role in that course, availability and the enrollment date, so the question "what is this student actually registered for" is answered in one search. Let the user jump straight from any row into that course's roster tab.

Course roster tab: for the course selected in the picker, show the full roster from Get Course Memberships with each person's name, username, email, role and last access, sorted with instructors and teaching assistants first. Load the available role options with Get Course Roles and let the user change someone's role inline, for example promoting a student to teaching assistant, with Update Membership. Removing someone uses Delete Course Membership behind a confirmation dialog that names both the person and the course. After a change, refresh just that row with Get Membership instead of reloading the entire roster.

Bulk enroll tab: the user supplies a Google Sheets spreadsheet ID and range, and the app reads the roster with Get Values. Match each row to a Blackboard user. Blackboard path IDs accept secondary ID prefixes (externalId:, userName:, emailAddress:), which is what makes spreadsheet matching practical when the sheet holds student emails or usernames rather than Blackboard primary keys. Use those prefixes first and fall back to a Get Users search when a row does not resolve cleanly.

The dry run preview before any write is the whole point, because bulk enrollment mistakes are painful to unwind in an LMS. Never write on load. Show a preview table that splits every row into three groups: will enroll, already enrolled (skip), and could not match (failure), with a plain reason on each skipped or failed row. Creating a membership that already exists returns a 409 conflict, so compare against the current roster first and mark those rows as skips rather than failures. Only after the user approves the preview does the app enroll the "will enroll" rows with Create Course Membership, using a role chosen for the batch. Show per row success or failure once the run finishes, and let the user copy or export the failed rows to fix and retry.

Every add, role change and removal appends a row to an audit tab in the same spreadsheet through Append Values, capturing the timestamp, who made the change, the action, the course, the person affected, the previous role and the new role. Write the audit row after the Blackboard call succeeds, and surface a visible warning if the audit append itself fails, so we always have a reliable record of who changed what and when.

Keep the interface dense and readable: table first layout, inline role dropdowns, clear empty and loading states, counts on each preview group, and errors shown next to the row that caused them rather than as a single generic banner.