This would need to emailing the member to advise them of the change and with a link to cancel or accept it, and timeout that allows the change. A similar process would need to happen to unlink an identity from a member. The timeout has to allow the change, otherwise an identity could be locked to a defunct account without being recoverable.
If the context identity is linked to a MemberKey, do not offer identities which are linked to a MemberKey because they're either already linked or cannot be linked because you can't combine two players that each have a MemberKey.
The UI for teams to link players should offer identities which are:
on the same team
if the context identity is linked to a MemberKey, only identities not already linked to any MemberKey (including the same one)
if the context identity is not linked to a MemberKey, only identities not already linked to the context identity
Note: _LinkedPlayers.cshtml used to have code that said includeLinkedToMember={!Model.Player.MemberKey.HasValue} before this requirement was changed to requiring a permission request.
This would need to emailing the member to advise them of the change and with a link to cancel or accept it, and timeout that allows the change. A similar process would need to happen to unlink an identity from a member. The timeout has to allow the change, otherwise an identity could be locked to a defunct account without being recoverable.
If the context identity is linked to a
MemberKey, do not offer identities which are linked to aMemberKeybecause they're either already linked or cannot be linked because you can't combine two players that each have aMemberKey.The UI for teams to link players should offer identities which are:
Note:
_LinkedPlayers.cshtmlused to have code that saidincludeLinkedToMember={!Model.Player.MemberKey.HasValue}before this requirement was changed to requiring a permission request.Update
Players.mdwhen done.