<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Cannot use member_email to login after changing the standard email in Email Deliverability</title>
    <link>https://community.hubspot.com/t5/Email-Deliverability/Cannot-use-member-email-to-login-after-changing-the-standard/m-p/1109961#M3416</link>
    <description>&lt;P&gt;Hi Team,&lt;/P&gt;&lt;P&gt;This is a time-sensitive issue. We are using &lt;STRONG&gt;HubSpot CMS Membership&lt;/STRONG&gt; for end users to log in to our company’s portal.&lt;/P&gt;&lt;P&gt;Currently, we allow users to update their &lt;STRONG&gt;communication email&lt;/STRONG&gt; via a form by capturing it in a custom email field which then updates the standard email field using the workflow. However, this process &amp;nbsp;also changes their &lt;STRONG&gt;login username&lt;/STRONG&gt;. Although the &lt;STRONG&gt;"member email"&lt;/STRONG&gt; remains unchanged, HubSpot still requires users to log in with the updated value in the &lt;STRONG&gt;email&lt;/STRONG&gt; field, overriding the original login credentials. This is not supposed to work like this.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;H3&gt;&lt;STRONG&gt;Use Case &amp;amp; Requirement&lt;/STRONG&gt;&lt;/H3&gt;&lt;P&gt;We need two separate email fields:&lt;/P&gt;&lt;OL&gt;&lt;LI&gt;&lt;STRONG&gt;Member Email (Login Email)&lt;/STRONG&gt; – Used for authentication and should remain unchanged.&lt;/LI&gt;&lt;LI&gt;&lt;STRONG&gt;Email (Communication Email)&lt;/STRONG&gt; – Can be updated by the user for receiving communications.&lt;/LI&gt;&lt;/OL&gt;&lt;P&gt;Initially, both field values are the same, but users should have the option to change their &lt;STRONG&gt;communication email&lt;/STRONG&gt; without affecting their &lt;STRONG&gt;login credentials&lt;/STRONG&gt;.&lt;/P&gt;&lt;P&gt;Could you advise on how to implement this ?&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Looking forward to your guidance.&lt;/P&gt;&lt;P&gt;Best regards,&lt;BR /&gt;Sreeju&lt;/P&gt;</description>
    <pubDate>Mon, 17 Feb 2025 10:18:07 GMT</pubDate>
    <dc:creator>Sreeju</dc:creator>
    <dc:date>2025-02-17T10:18:07Z</dc:date>
    <item>
      <title>Cannot use member_email to login after changing the standard email</title>
      <link>https://community.hubspot.com/t5/Email-Deliverability/Cannot-use-member-email-to-login-after-changing-the-standard/m-p/1109961#M3416</link>
      <description>&lt;P&gt;Hi Team,&lt;/P&gt;&lt;P&gt;This is a time-sensitive issue. We are using &lt;STRONG&gt;HubSpot CMS Membership&lt;/STRONG&gt; for end users to log in to our company’s portal.&lt;/P&gt;&lt;P&gt;Currently, we allow users to update their &lt;STRONG&gt;communication email&lt;/STRONG&gt; via a form by capturing it in a custom email field which then updates the standard email field using the workflow. However, this process &amp;nbsp;also changes their &lt;STRONG&gt;login username&lt;/STRONG&gt;. Although the &lt;STRONG&gt;"member email"&lt;/STRONG&gt; remains unchanged, HubSpot still requires users to log in with the updated value in the &lt;STRONG&gt;email&lt;/STRONG&gt; field, overriding the original login credentials. This is not supposed to work like this.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;H3&gt;&lt;STRONG&gt;Use Case &amp;amp; Requirement&lt;/STRONG&gt;&lt;/H3&gt;&lt;P&gt;We need two separate email fields:&lt;/P&gt;&lt;OL&gt;&lt;LI&gt;&lt;STRONG&gt;Member Email (Login Email)&lt;/STRONG&gt; – Used for authentication and should remain unchanged.&lt;/LI&gt;&lt;LI&gt;&lt;STRONG&gt;Email (Communication Email)&lt;/STRONG&gt; – Can be updated by the user for receiving communications.&lt;/LI&gt;&lt;/OL&gt;&lt;P&gt;Initially, both field values are the same, but users should have the option to change their &lt;STRONG&gt;communication email&lt;/STRONG&gt; without affecting their &lt;STRONG&gt;login credentials&lt;/STRONG&gt;.&lt;/P&gt;&lt;P&gt;Could you advise on how to implement this ?&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Looking forward to your guidance.&lt;/P&gt;&lt;P&gt;Best regards,&lt;BR /&gt;Sreeju&lt;/P&gt;</description>
      <pubDate>Mon, 17 Feb 2025 10:18:07 GMT</pubDate>
      <guid>https://community.hubspot.com/t5/Email-Deliverability/Cannot-use-member-email-to-login-after-changing-the-standard/m-p/1109961#M3416</guid>
      <dc:creator>Sreeju</dc:creator>
      <dc:date>2025-02-17T10:18:07Z</dc:date>
    </item>
    <item>
      <title>Re: Cannot use member_email to login after changing the standard email</title>
      <link>https://community.hubspot.com/t5/Email-Deliverability/Cannot-use-member-email-to-login-after-changing-the-standard/m-p/1110074#M3418</link>
      <description>&lt;P&gt;Hi &lt;SPAN style="background: var(--ck-color-mention-background); color: var(--ck-color-mention-text);"&gt;&lt;a href="https://community.hubspot.com/t5/user/viewprofilepage/user-id/901152"&gt;@Sreeju&lt;/a&gt;&lt;/SPAN&gt; and welcome, we are delighted to have you here! &lt;span class="lia-unicode-emoji" title=":party_popper:"&gt;🎉&lt;/span&gt;&lt;BR /&gt;&lt;BR /&gt;Thanks for asking the HubSpot Community!&lt;BR /&gt;&lt;BR /&gt;I understand that, &amp;nbsp;on a &lt;A href="https://knowledge.hubspot.com/inbox/set-up-a-customer-portal" target="_blank"&gt;customer portal&lt;/A&gt;, when a contact updates the subscription email, it also updates the login credentials. Please let me know if that's not the case.&lt;BR /&gt;&lt;BR /&gt;Here are some resources that might be of interest:&lt;BR /&gt;&lt;BR /&gt;- &lt;A href="https://knowledge.hubspot.com/marketing-email/manage-your-marketing-email-account-settings" target="_blank"&gt;Manage your default marketing email settings and tracking preferences&lt;/A&gt;&lt;BR /&gt;- &lt;A href="https://knowledge.hubspot.com/records/manage-your-subscription-preferences-and-types" target="_blank"&gt;Manage your contacts' messaging subscriptions&lt;/A&gt;&lt;BR /&gt;&lt;BR /&gt;I'd love to put you in touch with some of our Top Experts and Community Members: Hi &lt;SPAN style="background: var(--ck-color-mention-background); color: var(--ck-color-mention-text);"&gt;&lt;a href="https://community.hubspot.com/t5/user/viewprofilepage/user-id/640"&gt;@Lucila-Andimol&lt;/a&gt;&lt;/SPAN&gt;, &lt;SPAN style="background: var(--ck-color-mention-background); color: var(--ck-color-mention-text);"&gt;&lt;a href="https://community.hubspot.com/t5/user/viewprofilepage/user-id/547664"&gt;@DStaat&lt;/a&gt;&lt;/SPAN&gt;, &lt;SPAN style="background: var(--ck-color-mention-background); color: var(--ck-color-mention-text);"&gt;&lt;a href="https://community.hubspot.com/t5/user/viewprofilepage/user-id/363300"&gt;@Jnix284&lt;/a&gt;&lt;/SPAN&gt; and &lt;SPAN style="background: var(--ck-color-mention-background); color: var(--ck-color-mention-text);"&gt;&lt;a href="https://community.hubspot.com/t5/user/viewprofilepage/user-id/66301"&gt;@Bryantworks&lt;/a&gt;&lt;/SPAN&gt; do you have any insights to share to help &lt;SPAN style="background: var(--ck-color-mention-background); color: var(--ck-color-mention-text);"&gt;&lt;a href="https://community.hubspot.com/t5/user/viewprofilepage/user-id/901152"&gt;@Sreeju&lt;/a&gt;&lt;/SPAN&gt;, please?&lt;BR /&gt;&lt;BR /&gt;Also, I would recommend &lt;STRONG&gt;connecting with HubSpot Technical Support&lt;/STRONG&gt;, as Support is included in your subscription and they will be able to provide real-time assistance for this matter, including hopping on a screenshare if necessary.&lt;BR /&gt;&lt;BR /&gt;Have a lovely day and thanks so much! &lt;span class="lia-unicode-emoji" title=":red_heart:"&gt;❤️&lt;/span&gt;&lt;BR /&gt;&lt;BR /&gt;Best,&lt;BR /&gt;Bérangère&lt;/P&gt;</description>
      <pubDate>Mon, 17 Feb 2025 14:23:20 GMT</pubDate>
      <guid>https://community.hubspot.com/t5/Email-Deliverability/Cannot-use-member-email-to-login-after-changing-the-standard/m-p/1110074#M3418</guid>
      <dc:creator>BérangèreL</dc:creator>
      <dc:date>2025-02-17T14:23:20Z</dc:date>
    </item>
  </channel>
</rss>

