<?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>article No Email Address listed for Users in Qlik Cloud in Official Support Articles</title>
    <link>https://community.qlik.com/t5/Official-Support-Articles/No-Email-Address-listed-for-Users-in-Qlik-Cloud/ta-p/1774052</link>
    <description>&lt;P&gt;Users listed under the Management console do no show the Email address associated with the user.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&lt;span class="lia-inline-image-display-wrapper lia-image-align-center" image-alt="No_Email.png" style="width: 999px;"&gt;&lt;img src="https://community.qlik.com/t5/image/serverpage/image-id/46904i283D9875342676EC/image-size/large?v=v2&amp;amp;px=999" role="button" title="No_Email.png" alt="No_Email.png" /&gt;&lt;/span&gt;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;H4&gt;Environment&lt;/H4&gt;
&lt;UL&gt;
&lt;LI&gt;Qlik Sense Enterprise SaaS&lt;/LI&gt;
&lt;/UL&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&lt;STRONG&gt;Disclaimer:&lt;/STRONG&gt; The information below is subject to change as the Identity Providers continue to expand their solutions.&lt;/P&gt;
&lt;H3&gt;Cause&lt;/H3&gt;
&lt;P&gt;The identity provider (IdP) either has not provided evidence to Qlik Sense that the user's email address has been verified, or Qlik Sense has failed to process the specific IdP's non-standard claim name that indicates that the email has actually been verified.&lt;/P&gt;
&lt;P&gt;&lt;SPAN&gt;Some Identity Providers allow the administrators to create users without a validation process. This is convenient but not recommended for security reasons, as the&amp;nbsp;identity associated with an unverified email address is less trusted. Other vendors require a verification process but then may not supply the &lt;FONT face="courier new,courier"&gt;email_verified&lt;/FONT&gt; claim information to Qlik Sense Enterprise SaaS (a violation of the OpenId Connect specification perhaps?). Still others do it well but the name of the claim is not the standard name.&amp;nbsp;&lt;/SPAN&gt;&lt;/P&gt;
&lt;P&gt;How do the popular Identity Provider vendors handle the &lt;FONT face="courier new,courier"&gt;email_verified&lt;/FONT&gt; claim?&lt;/P&gt;
&lt;P&gt;The following vendors are known to have an email verification process that when exercised by the Identity Provider administrator provides the &lt;FONT face="courier new,courier"&gt;email_verified&lt;/FONT&gt; claim to &lt;SPAN&gt;Qlik Sense Enterprise SaaS&amp;nbsp;&lt;/SPAN&gt;at login without any special mapping:&lt;/P&gt;
&lt;UL&gt;
&lt;LI&gt;Okta, Auth0, Onelogin (v2), Google Identity, IBM Security Verify&lt;/LI&gt;
&lt;/UL&gt;
&lt;P&gt;&lt;BR /&gt;The following vendors support an email verification process but do not provide the necessary email_verified claim easily and so can be fixed within &lt;SPAN&gt;Qlik Sense Enterprise SaaS&amp;nbsp;&lt;/SPAN&gt;via the Email Verified Override toggle:&lt;/P&gt;
&lt;UL&gt;
&lt;LI&gt;Azure AD&lt;/LI&gt;
&lt;/UL&gt;
&lt;H3&gt;Resolution&lt;/H3&gt;
&lt;P&gt;There is one official resolution that consists of ensuring&amp;nbsp;that the specific IdP has verified the user's email address and has been configured to indicate this with the claim &lt;FONT face="courier new,courier"&gt;"email_verified":true&lt;/FONT&gt;.&lt;/P&gt;
&lt;P&gt;Note that two workaround are included further down in the article in the case of the IdP not providing a standard email verification claim field or simply not supporting it.&lt;/P&gt;
&lt;P&gt;&lt;SPAN&gt;It's difficult to provide blanket instructions on how to configure proper email verification as each Identity Provider vendor handles it differently.&amp;nbsp;Details for each Identity Provider vendor tested to work with Qlik Sense Enterprise SaaS (there are many!) is beyond the scope of this article or Qlik Support, and should be performed by the administrator.&amp;nbsp;We recommend a search for &lt;FONT face="courier new,courier"&gt;email_verified&lt;/FONT&gt; within your Identity Providers documentation on the web or look for other Qlik Community articles on this topic for the Identity Provider vendor of interest.&lt;/SPAN&gt;&lt;/P&gt;
&lt;P&gt;In order to confirm the issue lies on the IdP's claim response, logon with the specific user to the Qlik Sense SaaS tenant, open a new browser tab, and use the following URL to retrieve the claims provided by the IdP:&lt;/P&gt;
&lt;P&gt;&lt;FONT face="courier new,courier"&gt;https://&amp;lt;tenantName&amp;gt;.&amp;lt;region&amp;gt;.qlikcloud.com/api/v1/diagnose-claims&lt;/FONT&gt;&lt;/P&gt;
&lt;P&gt;Here's an example JSON string response:&lt;/P&gt;
&lt;P&gt;&lt;span class="lia-inline-image-display-wrapper lia-image-align-center" image-alt="Claims.png" style="width: 767px;"&gt;&lt;img src="https://community.qlik.com/t5/image/serverpage/image-id/48082iCF45A1D9A25FC253/image-size/large?v=v2&amp;amp;px=999" role="button" title="Claims.png" alt="Claims.png" /&gt;&lt;/span&gt;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;In the response above we see &lt;FONT face="courier new,courier"&gt;"email_verified":true&lt;/FONT&gt; in three places, for which we care only to the ones under the &lt;FONT face="courier new,courier"&gt;claimsFromIdp&lt;/FONT&gt; and &lt;FONT face="courier new,courier"&gt;mappedClaims&lt;/FONT&gt; lists.&lt;/P&gt;
&lt;P&gt;With a response from the IdP such as the one above, it would be expected that the user's Email field would be populated with the user's email in the Management Console.&lt;/P&gt;
&lt;P&gt;Another way to check on the above is to login with the specific user to the Management Console and under Identity Providers click on the &lt;STRONG&gt;Validate&lt;/STRONG&gt; option.&lt;/P&gt;
&lt;P&gt;&lt;span class="lia-inline-image-display-wrapper lia-image-align-center" image-alt="ValidateViaIdP.png" style="width: 999px;"&gt;&lt;img src="https://community.qlik.com/t5/image/serverpage/image-id/46895i33B355E0B2CE6B78/image-size/large?v=v2&amp;amp;px=999" role="button" title="ValidateViaIdP.png" alt="ValidateViaIdP.png" /&gt;&lt;/span&gt;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&lt;STRONG&gt;Example:&lt;/STRONG&gt;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&lt;span class="lia-inline-image-display-wrapper lia-image-align-center" image-alt="ValidateViaIdP1.png" style="width: 434px;"&gt;&lt;img src="https://community.qlik.com/t5/image/serverpage/image-id/46896iC011B179D01E75B7/image-dimensions/434x680?v=v2" width="434" height="680" role="button" title="ValidateViaIdP1.png" alt="ValidateViaIdP1.png" /&gt;&lt;/span&gt;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;After supplying login credentials, the claims validation page will appear and show the email address and either&amp;nbsp;&lt;STRONG&gt;email_verified&lt;/STRONG&gt;&amp;nbsp;as&amp;nbsp;&lt;STRONG&gt;true,&lt;/STRONG&gt; or a warning message.&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&lt;span class="lia-inline-image-display-wrapper lia-image-align-center" image-alt="ValidateViaIdP2.png" style="width: 425px;"&gt;&lt;img src="https://community.qlik.com/t5/image/serverpage/image-id/46900iA6F80A0C07E2EC2A/image-dimensions/425x679?v=v2" width="425" height="679" role="button" title="ValidateViaIdP2.png" alt="ValidateViaIdP2.png" /&gt;&lt;/span&gt;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&lt;span class="lia-inline-image-display-wrapper lia-image-align-center" image-alt="ValidateViaIdP2.png" style="width: 0px;"&gt;&lt;img src="https://community.qlik.com/t5/image/serverpage/image-id/46900iA6F80A0C07E2EC2A/image-size/large?v=v2&amp;amp;px=999" width="0" height="0" role="button" title="ValidateViaIdP2.png" alt="ValidateViaIdP2.png" /&gt;&lt;/span&gt;&lt;/P&gt;
&lt;H3&gt;Workaround(s):&lt;/H3&gt;
&lt;P&gt;&lt;STRONG&gt;1.&lt;/STRONG&gt; If the IdP is providing &lt;STRONG&gt;email_verified&lt;/STRONG&gt; claim but has named it different, adjust the Claims Mapping under the &lt;STRONG&gt;Identity Provider&lt;/STRONG&gt; configuration via the Management Console.&lt;/P&gt;
&lt;P&gt;&lt;STRONG&gt;Example:&lt;/STRONG&gt;&lt;/P&gt;
&lt;P&gt;&lt;STRONG&gt;&lt;span class="lia-inline-image-display-wrapper lia-image-align-center" image-alt="ClaimsMapping1.png" style="width: 425px;"&gt;&lt;img src="https://community.qlik.com/t5/image/serverpage/image-id/46902i285C2331A898F214/image-dimensions/425x617?v=v2" width="425" height="617" role="button" title="ClaimsMapping1.png" alt="ClaimsMapping1.png" /&gt;&lt;/span&gt;&lt;/STRONG&gt;&lt;/P&gt;
&lt;P&gt;&lt;STRONG&gt;&amp;nbsp;&lt;/STRONG&gt;&lt;/P&gt;
&lt;P&gt;&lt;STRONG&gt;2. &lt;/STRONG&gt;If the IdP does not support the &lt;STRONG&gt;email_verfied&lt;/STRONG&gt; claim, set the option&amp;nbsp;&lt;STRONG&gt;Email Verified Override&lt;/STRONG&gt;. This is only available for specific IdPs such as when selecting &lt;STRONG&gt;Azure AD&lt;/STRONG&gt; in the configuration. The option is then available under the Advance settings.&lt;/P&gt;
&lt;P&gt;&lt;span class="lia-inline-image-display-wrapper lia-image-align-center" image-alt="ClaimsMapping2.png" style="width: 425px;"&gt;&lt;img src="https://community.qlik.com/t5/image/serverpage/image-id/46903i2FEA4F84E43FF6CF/image-dimensions/425x638?v=v2" width="425" height="638" role="button" title="ClaimsMapping2.png" alt="ClaimsMapping2.png" /&gt;&lt;/span&gt;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;H3&gt;Related Content&lt;/H3&gt;
&lt;UL&gt;
&lt;LI&gt;&lt;A href="https://community.qlik.com/t5/Support-Knowledge-Base/How-to-Enable-User-Groups-in-Qlik-Sense-Enterprise-SaaS/ta-p/1735945" target="_blank" rel="noopener"&gt;How to Enable User Groups in Qlik Sense Enterprise SaaS&lt;/A&gt;&amp;nbsp;&lt;/LI&gt;
&lt;/UL&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
    <pubDate>Tue, 10 May 2022 19:01:03 GMT</pubDate>
    <dc:creator>Andre_Sostizzo</dc:creator>
    <dc:date>2022-05-10T19:01:03Z</dc:date>
    <item>
      <title>No Email Address listed for Users in Qlik Cloud</title>
      <link>https://community.qlik.com/t5/Official-Support-Articles/No-Email-Address-listed-for-Users-in-Qlik-Cloud/ta-p/1774052</link>
      <description>&lt;P&gt;Users listed under the Management console do no show the Email address associated with the user.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&lt;span class="lia-inline-image-display-wrapper lia-image-align-center" image-alt="No_Email.png" style="width: 999px;"&gt;&lt;img src="https://community.qlik.com/t5/image/serverpage/image-id/46904i283D9875342676EC/image-size/large?v=v2&amp;amp;px=999" role="button" title="No_Email.png" alt="No_Email.png" /&gt;&lt;/span&gt;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;H4&gt;Environment&lt;/H4&gt;
&lt;UL&gt;
&lt;LI&gt;Qlik Sense Enterprise SaaS&lt;/LI&gt;
&lt;/UL&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&lt;STRONG&gt;Disclaimer:&lt;/STRONG&gt; The information below is subject to change as the Identity Providers continue to expand their solutions.&lt;/P&gt;
&lt;H3&gt;Cause&lt;/H3&gt;
&lt;P&gt;The identity provider (IdP) either has not provided evidence to Qlik Sense that the user's email address has been verified, or Qlik Sense has failed to process the specific IdP's non-standard claim name that indicates that the email has actually been verified.&lt;/P&gt;
&lt;P&gt;&lt;SPAN&gt;Some Identity Providers allow the administrators to create users without a validation process. This is convenient but not recommended for security reasons, as the&amp;nbsp;identity associated with an unverified email address is less trusted. Other vendors require a verification process but then may not supply the &lt;FONT face="courier new,courier"&gt;email_verified&lt;/FONT&gt; claim information to Qlik Sense Enterprise SaaS (a violation of the OpenId Connect specification perhaps?). Still others do it well but the name of the claim is not the standard name.&amp;nbsp;&lt;/SPAN&gt;&lt;/P&gt;
&lt;P&gt;How do the popular Identity Provider vendors handle the &lt;FONT face="courier new,courier"&gt;email_verified&lt;/FONT&gt; claim?&lt;/P&gt;
&lt;P&gt;The following vendors are known to have an email verification process that when exercised by the Identity Provider administrator provides the &lt;FONT face="courier new,courier"&gt;email_verified&lt;/FONT&gt; claim to &lt;SPAN&gt;Qlik Sense Enterprise SaaS&amp;nbsp;&lt;/SPAN&gt;at login without any special mapping:&lt;/P&gt;
&lt;UL&gt;
&lt;LI&gt;Okta, Auth0, Onelogin (v2), Google Identity, IBM Security Verify&lt;/LI&gt;
&lt;/UL&gt;
&lt;P&gt;&lt;BR /&gt;The following vendors support an email verification process but do not provide the necessary email_verified claim easily and so can be fixed within &lt;SPAN&gt;Qlik Sense Enterprise SaaS&amp;nbsp;&lt;/SPAN&gt;via the Email Verified Override toggle:&lt;/P&gt;
&lt;UL&gt;
&lt;LI&gt;Azure AD&lt;/LI&gt;
&lt;/UL&gt;
&lt;H3&gt;Resolution&lt;/H3&gt;
&lt;P&gt;There is one official resolution that consists of ensuring&amp;nbsp;that the specific IdP has verified the user's email address and has been configured to indicate this with the claim &lt;FONT face="courier new,courier"&gt;"email_verified":true&lt;/FONT&gt;.&lt;/P&gt;
&lt;P&gt;Note that two workaround are included further down in the article in the case of the IdP not providing a standard email verification claim field or simply not supporting it.&lt;/P&gt;
&lt;P&gt;&lt;SPAN&gt;It's difficult to provide blanket instructions on how to configure proper email verification as each Identity Provider vendor handles it differently.&amp;nbsp;Details for each Identity Provider vendor tested to work with Qlik Sense Enterprise SaaS (there are many!) is beyond the scope of this article or Qlik Support, and should be performed by the administrator.&amp;nbsp;We recommend a search for &lt;FONT face="courier new,courier"&gt;email_verified&lt;/FONT&gt; within your Identity Providers documentation on the web or look for other Qlik Community articles on this topic for the Identity Provider vendor of interest.&lt;/SPAN&gt;&lt;/P&gt;
&lt;P&gt;In order to confirm the issue lies on the IdP's claim response, logon with the specific user to the Qlik Sense SaaS tenant, open a new browser tab, and use the following URL to retrieve the claims provided by the IdP:&lt;/P&gt;
&lt;P&gt;&lt;FONT face="courier new,courier"&gt;https://&amp;lt;tenantName&amp;gt;.&amp;lt;region&amp;gt;.qlikcloud.com/api/v1/diagnose-claims&lt;/FONT&gt;&lt;/P&gt;
&lt;P&gt;Here's an example JSON string response:&lt;/P&gt;
&lt;P&gt;&lt;span class="lia-inline-image-display-wrapper lia-image-align-center" image-alt="Claims.png" style="width: 767px;"&gt;&lt;img src="https://community.qlik.com/t5/image/serverpage/image-id/48082iCF45A1D9A25FC253/image-size/large?v=v2&amp;amp;px=999" role="button" title="Claims.png" alt="Claims.png" /&gt;&lt;/span&gt;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;In the response above we see &lt;FONT face="courier new,courier"&gt;"email_verified":true&lt;/FONT&gt; in three places, for which we care only to the ones under the &lt;FONT face="courier new,courier"&gt;claimsFromIdp&lt;/FONT&gt; and &lt;FONT face="courier new,courier"&gt;mappedClaims&lt;/FONT&gt; lists.&lt;/P&gt;
&lt;P&gt;With a response from the IdP such as the one above, it would be expected that the user's Email field would be populated with the user's email in the Management Console.&lt;/P&gt;
&lt;P&gt;Another way to check on the above is to login with the specific user to the Management Console and under Identity Providers click on the &lt;STRONG&gt;Validate&lt;/STRONG&gt; option.&lt;/P&gt;
&lt;P&gt;&lt;span class="lia-inline-image-display-wrapper lia-image-align-center" image-alt="ValidateViaIdP.png" style="width: 999px;"&gt;&lt;img src="https://community.qlik.com/t5/image/serverpage/image-id/46895i33B355E0B2CE6B78/image-size/large?v=v2&amp;amp;px=999" role="button" title="ValidateViaIdP.png" alt="ValidateViaIdP.png" /&gt;&lt;/span&gt;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&lt;STRONG&gt;Example:&lt;/STRONG&gt;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&lt;span class="lia-inline-image-display-wrapper lia-image-align-center" image-alt="ValidateViaIdP1.png" style="width: 434px;"&gt;&lt;img src="https://community.qlik.com/t5/image/serverpage/image-id/46896iC011B179D01E75B7/image-dimensions/434x680?v=v2" width="434" height="680" role="button" title="ValidateViaIdP1.png" alt="ValidateViaIdP1.png" /&gt;&lt;/span&gt;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;After supplying login credentials, the claims validation page will appear and show the email address and either&amp;nbsp;&lt;STRONG&gt;email_verified&lt;/STRONG&gt;&amp;nbsp;as&amp;nbsp;&lt;STRONG&gt;true,&lt;/STRONG&gt; or a warning message.&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&lt;span class="lia-inline-image-display-wrapper lia-image-align-center" image-alt="ValidateViaIdP2.png" style="width: 425px;"&gt;&lt;img src="https://community.qlik.com/t5/image/serverpage/image-id/46900iA6F80A0C07E2EC2A/image-dimensions/425x679?v=v2" width="425" height="679" role="button" title="ValidateViaIdP2.png" alt="ValidateViaIdP2.png" /&gt;&lt;/span&gt;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&lt;span class="lia-inline-image-display-wrapper lia-image-align-center" image-alt="ValidateViaIdP2.png" style="width: 0px;"&gt;&lt;img src="https://community.qlik.com/t5/image/serverpage/image-id/46900iA6F80A0C07E2EC2A/image-size/large?v=v2&amp;amp;px=999" width="0" height="0" role="button" title="ValidateViaIdP2.png" alt="ValidateViaIdP2.png" /&gt;&lt;/span&gt;&lt;/P&gt;
&lt;H3&gt;Workaround(s):&lt;/H3&gt;
&lt;P&gt;&lt;STRONG&gt;1.&lt;/STRONG&gt; If the IdP is providing &lt;STRONG&gt;email_verified&lt;/STRONG&gt; claim but has named it different, adjust the Claims Mapping under the &lt;STRONG&gt;Identity Provider&lt;/STRONG&gt; configuration via the Management Console.&lt;/P&gt;
&lt;P&gt;&lt;STRONG&gt;Example:&lt;/STRONG&gt;&lt;/P&gt;
&lt;P&gt;&lt;STRONG&gt;&lt;span class="lia-inline-image-display-wrapper lia-image-align-center" image-alt="ClaimsMapping1.png" style="width: 425px;"&gt;&lt;img src="https://community.qlik.com/t5/image/serverpage/image-id/46902i285C2331A898F214/image-dimensions/425x617?v=v2" width="425" height="617" role="button" title="ClaimsMapping1.png" alt="ClaimsMapping1.png" /&gt;&lt;/span&gt;&lt;/STRONG&gt;&lt;/P&gt;
&lt;P&gt;&lt;STRONG&gt;&amp;nbsp;&lt;/STRONG&gt;&lt;/P&gt;
&lt;P&gt;&lt;STRONG&gt;2. &lt;/STRONG&gt;If the IdP does not support the &lt;STRONG&gt;email_verfied&lt;/STRONG&gt; claim, set the option&amp;nbsp;&lt;STRONG&gt;Email Verified Override&lt;/STRONG&gt;. This is only available for specific IdPs such as when selecting &lt;STRONG&gt;Azure AD&lt;/STRONG&gt; in the configuration. The option is then available under the Advance settings.&lt;/P&gt;
&lt;P&gt;&lt;span class="lia-inline-image-display-wrapper lia-image-align-center" image-alt="ClaimsMapping2.png" style="width: 425px;"&gt;&lt;img src="https://community.qlik.com/t5/image/serverpage/image-id/46903i2FEA4F84E43FF6CF/image-dimensions/425x638?v=v2" width="425" height="638" role="button" title="ClaimsMapping2.png" alt="ClaimsMapping2.png" /&gt;&lt;/span&gt;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;H3&gt;Related Content&lt;/H3&gt;
&lt;UL&gt;
&lt;LI&gt;&lt;A href="https://community.qlik.com/t5/Support-Knowledge-Base/How-to-Enable-User-Groups-in-Qlik-Sense-Enterprise-SaaS/ta-p/1735945" target="_blank" rel="noopener"&gt;How to Enable User Groups in Qlik Sense Enterprise SaaS&lt;/A&gt;&amp;nbsp;&lt;/LI&gt;
&lt;/UL&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Tue, 10 May 2022 19:01:03 GMT</pubDate>
      <guid>https://community.qlik.com/t5/Official-Support-Articles/No-Email-Address-listed-for-Users-in-Qlik-Cloud/ta-p/1774052</guid>
      <dc:creator>Andre_Sostizzo</dc:creator>
      <dc:date>2022-05-10T19:01:03Z</dc:date>
    </item>
  </channel>
</rss>

