We had an instance where a committee member was imported from LionPath while they were employed by Penn State. They then left Penn State before the review process, so when the review process came along, and admin changed the email to a non-PSU email. However, the committee member still had an Access ID and a committee member token was not generated. We need to look at the code an determine why the Access ID was not removed and a token was not generated when the email was changed. Ideally, we want these things to happen, even for committee members imported from LionPath.
We had an instance where a committee member was imported from LionPath while they were employed by Penn State. They then left Penn State before the review process, so when the review process came along, and admin changed the email to a non-PSU email. However, the committee member still had an Access ID and a committee member token was not generated. We need to look at the code an determine why the Access ID was not removed and a token was not generated when the email was changed. Ideally, we want these things to happen, even for committee members imported from LionPath.