Improve importer experience
Currently, importing exercise data is a huge mess. There are lots of smaller tools in the workflow that could possibly be combined and be provided as a general solution elsewhere. One option is to let hector perform most of the tasks, which would include sending mails, setting passwords (currently broken), mapping of exercise groups and figuring out which students already exist in the system (this could be rather tricky and hacky).
I prefer to handle the complete setup of an instance for exercise groups a bit differently. I'd like to propose some kind of endpoint where, once all students have been assigned to their groups, a reviewer can upload a JSON file which includes the relevant student account data. This way, we don't have to mix things into hector that probaly should not be there (like setting passwords and figuring out which students already exist in the system, etc.). However, to reliably apply this approach we would have to rely on the flexnow student lists, which sometimes come with a slight delay (in this case, grady won't be ready for use until flexnow's student lists are available).