You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently creating a Staff user or External Examiner user requires the underlying User object to be created (often with an unnecessary password - since in production I am using CAS), and then the linked Staff object to be created, or ExternalExaminer object.
It would be useful to have a single admin form for each of these use cases. In a perfect world, there would be self sign-up, but there might be security issues involved in that - well, if the WorkPackage was selectable by the user without intervention.
The text was updated successfully, but these errors were encountered:
Currently creating a Staff user or External Examiner user requires the underlying User object to be created (often with an unnecessary password - since in production I am using CAS), and then the linked Staff object to be created, or ExternalExaminer object.
It would be useful to have a single admin form for each of these use cases. In a perfect world, there would be self sign-up, but there might be security issues involved in that - well, if the WorkPackage was selectable by the user without intervention.
The text was updated successfully, but these errors were encountered: