<?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 Security Example: QMC Access using Custom property in Official Support Articles</title>
    <link>https://community.qlik.com/t5/Official-Support-Articles/Security-Example-QMC-Access-using-Custom-property/ta-p/1717286</link>
    <description>&lt;P&gt;How to create a custom rule for Qlik Sense Management Console access using custom properties.&lt;BR /&gt;&lt;BR /&gt;&lt;STRONG&gt;Example Scenario: &lt;/STRONG&gt;Development Team with 2 users User1 and User2 need access to QMC Sections like &lt;STRONG&gt;App, AppObjects, Stream, Tasks, Data Connection, Users, Audit, Security Rule, Tag.&lt;/STRONG&gt; They should have Read, Create and edit Access for these resources. Also, they should be restricted with the selected app and streams.&lt;BR /&gt;&amp;nbsp;&lt;/P&gt;
&lt;H3&gt;&lt;STRONG&gt;&lt;STRONG&gt;&lt;STRONG&gt;Resolution:&lt;/STRONG&gt;&lt;/STRONG&gt;&lt;/STRONG&gt;&lt;/H3&gt;
&lt;P&gt;&lt;BR /&gt;This is just a basic rule to achieve the scenarios. any additional changes on it should be implemented with proper validations. Since creating custom rules are competently based on individual requirements. For any further details please refer &lt;A href="http://help.qlik.com/" target="_blank" rel="noopener"&gt;Help.qlik.com &lt;/A&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;STRONG&gt;Note: &lt;/STRONG&gt;Security Rules can be implemented in different methods based on business requirement. There is no standard steps followed,&amp;nbsp;however when working with the rule we need to ensure how the resource and&amp;nbsp;filters are affecting the existing default and custom rules.&lt;BR /&gt;&lt;BR /&gt;&lt;EM&gt;Refer to the Attached Document&lt;/EM&gt;&lt;/P&gt;</description>
    <pubDate>Thu, 11 Nov 2021 14:48:03 GMT</pubDate>
    <dc:creator>Sonja_Bauernfeind</dc:creator>
    <dc:date>2021-11-11T14:48:03Z</dc:date>
    <item>
      <title>Security Example: QMC Access using Custom property</title>
      <link>https://community.qlik.com/t5/Official-Support-Articles/Security-Example-QMC-Access-using-Custom-property/ta-p/1717286</link>
      <description>&lt;P&gt;How to create a custom rule for Qlik Sense Management Console access using custom properties.&lt;BR /&gt;&lt;BR /&gt;&lt;STRONG&gt;Example Scenario: &lt;/STRONG&gt;Development Team with 2 users User1 and User2 need access to QMC Sections like &lt;STRONG&gt;App, AppObjects, Stream, Tasks, Data Connection, Users, Audit, Security Rule, Tag.&lt;/STRONG&gt; They should have Read, Create and edit Access for these resources. Also, they should be restricted with the selected app and streams.&lt;BR /&gt;&amp;nbsp;&lt;/P&gt;
&lt;H3&gt;&lt;STRONG&gt;&lt;STRONG&gt;&lt;STRONG&gt;Resolution:&lt;/STRONG&gt;&lt;/STRONG&gt;&lt;/STRONG&gt;&lt;/H3&gt;
&lt;P&gt;&lt;BR /&gt;This is just a basic rule to achieve the scenarios. any additional changes on it should be implemented with proper validations. Since creating custom rules are competently based on individual requirements. For any further details please refer &lt;A href="http://help.qlik.com/" target="_blank" rel="noopener"&gt;Help.qlik.com &lt;/A&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;STRONG&gt;Note: &lt;/STRONG&gt;Security Rules can be implemented in different methods based on business requirement. There is no standard steps followed,&amp;nbsp;however when working with the rule we need to ensure how the resource and&amp;nbsp;filters are affecting the existing default and custom rules.&lt;BR /&gt;&lt;BR /&gt;&lt;EM&gt;Refer to the Attached Document&lt;/EM&gt;&lt;/P&gt;</description>
      <pubDate>Thu, 11 Nov 2021 14:48:03 GMT</pubDate>
      <guid>https://community.qlik.com/t5/Official-Support-Articles/Security-Example-QMC-Access-using-Custom-property/ta-p/1717286</guid>
      <dc:creator>Sonja_Bauernfeind</dc:creator>
      <dc:date>2021-11-11T14:48:03Z</dc:date>
    </item>
  </channel>
</rss>

