I suspect this is counter-productive, but is there a way to lock modules in the blueprint so that the receiving faculty can not delete them? Meaning, after building classes from the blueprint, we do not want faculty deleting modules. If the original set of modules in the blueprint is 8, then there should be at least 8 when IDs, Deans, other faculty-admin pays a quick visit.