<?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 Controlling access in Qlik Management Console to Custom Properties and Tags in Management &amp; Governance</title>
    <link>https://community.qlik.com/t5/Management-Governance/Controlling-access-in-Qlik-Management-Console-to-Custom/m-p/2108409#M29779</link>
    <description>&lt;P&gt;Use case: &lt;LI-PRODUCT title="Qlik Sense Enterprise on Windows" id="qlikSenseEnterpriseWindows"&gt;&lt;/LI-PRODUCT&gt;&amp;nbsp;Qlik Management Console has &lt;STRONG&gt;several departmental Admins&lt;/STRONG&gt;. Each admin can see only their own team's resources (apps, streams, data connections, etc.). This was achieved through a number of security rules that check the owner of the resource and the user group he/she belongs to (via a custom property value). However, &lt;STRONG&gt;Custom Properties&lt;/STRONG&gt; and &lt;STRONG&gt;Tags&lt;/STRONG&gt; don't have an owner. As a result, ALL admins see ALL custom properties or tags, regardless of who created them. It makes the view congested and creates a risk of admins cross-editing Custom Properties or Tags. Is there a way to show select custom properties and tags to a select group, and &lt;STRONG&gt;hide the rest&lt;/STRONG&gt;?&lt;/P&gt;</description>
    <pubDate>Tue, 22 Aug 2023 12:10:02 GMT</pubDate>
    <dc:creator>chiarusya</dc:creator>
    <dc:date>2023-08-22T12:10:02Z</dc:date>
    <item>
      <title>Controlling access in Qlik Management Console to Custom Properties and Tags</title>
      <link>https://community.qlik.com/t5/Management-Governance/Controlling-access-in-Qlik-Management-Console-to-Custom/m-p/2108409#M29779</link>
      <description>&lt;P&gt;Use case: &lt;LI-PRODUCT title="Qlik Sense Enterprise on Windows" id="qlikSenseEnterpriseWindows"&gt;&lt;/LI-PRODUCT&gt;&amp;nbsp;Qlik Management Console has &lt;STRONG&gt;several departmental Admins&lt;/STRONG&gt;. Each admin can see only their own team's resources (apps, streams, data connections, etc.). This was achieved through a number of security rules that check the owner of the resource and the user group he/she belongs to (via a custom property value). However, &lt;STRONG&gt;Custom Properties&lt;/STRONG&gt; and &lt;STRONG&gt;Tags&lt;/STRONG&gt; don't have an owner. As a result, ALL admins see ALL custom properties or tags, regardless of who created them. It makes the view congested and creates a risk of admins cross-editing Custom Properties or Tags. Is there a way to show select custom properties and tags to a select group, and &lt;STRONG&gt;hide the rest&lt;/STRONG&gt;?&lt;/P&gt;</description>
      <pubDate>Tue, 22 Aug 2023 12:10:02 GMT</pubDate>
      <guid>https://community.qlik.com/t5/Management-Governance/Controlling-access-in-Qlik-Management-Console-to-Custom/m-p/2108409#M29779</guid>
      <dc:creator>chiarusya</dc:creator>
      <dc:date>2023-08-22T12:10:02Z</dc:date>
    </item>
    <item>
      <title>Re: Controlling access in Qlik Management Console to Custom Properties and Tags</title>
      <link>https://community.qlik.com/t5/Management-Governance/Controlling-access-in-Qlik-Management-Console-to-Custom/m-p/2108660#M29780</link>
      <description>&lt;P&gt;Hi, I would suggest opening an Idealation for this issue.&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&lt;A href="https://community.qlik.com/t5/Get-Started/Ideation-Guidelines-How-to-Submit-an-Idea/ta-p/1960234" target="_blank"&gt;https://community.qlik.com/t5/Get-Started/Ideation-Guidelines-How-to-Submit-an-Idea/ta-p/1960234&lt;/A&gt;&lt;/P&gt;</description>
      <pubDate>Tue, 22 Aug 2023 19:09:56 GMT</pubDate>
      <guid>https://community.qlik.com/t5/Management-Governance/Controlling-access-in-Qlik-Management-Console-to-Custom/m-p/2108660#M29780</guid>
      <dc:creator>Alan_Slaughter</dc:creator>
      <dc:date>2023-08-22T19:09:56Z</dc:date>
    </item>
  </channel>
</rss>

