Duplicate Email Address Warning
If you send a Portal invitation email during the process of creating a new contact, the system will automatically check to make sure that the new contact's email address isn't already associated with one of your existing contacts. In the example below, the new contact's email address is already being used by an existing contact.
If the system detects that the email address is associated with an existing contact, a notification lets you know that the email address is already in use. Click Cancel to change the new contact's email address, or click Continue to create the contact with the duplicate email address. If you click Continue the new contact will not be able to use the Portal and no Portal invitation will be sent.
Transfer Portal Username to a Different Contact
When you have multiple contacts with the same primary email address, you may want to transfer the Portal Username from one contact to another contact. To transfer the Portal Username to a different contact, go to Contact Management, select the Contact that does not currently access to the Portal, go to their Portal tab, and click Invite to Portal.
A popup alerts you that the email address is already being used as a Portal Username by another one of your contacts. Click Continue to transfer the Portal Username to the current contact. The contact will now be able to login to the Portal using their primary email address as their username.
Please note that the password associated with the Portal does not change when you transfer the Portal Username. If necessary, the contact can use the Forgot Password link on the Portal log in page to reset the password. Alternatively, you can use the Reset Account option on the Portal Tab in Contact Management to send the contact a password reset email.
Once you have transferred the Portal Username from one contact to another, the Portal belongs to the new contact. The new contact will not see the News Feed, Saved Searches, or Saved Listings associated with the previous contact's Portal usage.
No comments:
Post a Comment