It happens, not often, but regularly that our SIS-system introduces duplicates of an individual, that then subsequently gets merged in the SIS-system. To keep our Canvas in step with the SIS-system, we then manually merge these duplicates (or delete if one of the accounts never have been used).
After merging, we then proceed to delete the now dysfunctional SIS-based login for the deleted account. But I am unable to delete the dysfunctional email address associated with the deleted user; either via the gui or via api (via api I get "user not authorized", and my authentication is root account Admin account, as high as it possible to set). It seems that this is still classed as an institutional email address even after having been merged.
I know there is a workaround to temporarily allow users to remove their institutional email addresses, but I would very much not have to take the risk that a trigger happy user does that during the short window I would need to leave this possibility open.
Is there really no way to in the merging process state that the emails of the deleted user should no longer be protected like this, I mean no longer considered to be an institutional email address? Or an additional api call I could make to set that flag? I cannot see it exposed anywhere...
Ngl, in my eyes it is a bug that a single user account can have more than one email address protected as an institutional email address...
