Details
-
Type: Improvement
-
Status: Closed
-
Priority: Major
-
Resolution: Fixed
-
Affects Version/s: None
-
Fix Version/s: 2.1.0
-
Component/s: None
-
Labels:None
-
Sprint:Sprint 10 - Cumberland
Description
in the event a subscriber is updated from v. 2.0.2.1 to v. 2.1x - it is possible that the user updated the Contact Email in the UI but was not saved in the db (while running v.2.0.2.1).
there is a SECURITY RISK that clicking the SEND INVITE button will send an activation email to the wrong user who will be able to create credentials to log in to the merchant dashboard that they were once (but no longer) involved with.
The Send Invite button should be greyed out or have some visual indicator to raise a support ticket to resolve this if it is noted that the Contact Email displayed in the UI is not the same as the Contact Email stored in the db.