<?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 How to implement the section access for Hierarchy level roles in App Development</title>
    <link>https://community.qlik.com/t5/App-Development/How-to-implement-the-section-access-for-Hierarchy-level-roles/m-p/2437717#M97078</link>
    <description>&lt;P&gt;&lt;SPAN&gt;Hi,&amp;nbsp;&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;I would like to set up section access for our data, organized into three levels: Board, School, and Class. I have attached two snapshots for reference, which show the hierarchy in both lists (Sample&amp;nbsp;file for better understanding, note we have&amp;nbsp;client data which is present in this way only to show relationships between each other) and&amp;nbsp;flowchart form. Essentially, if a user belongs to the Board Group, they should be able to see all the data for all schools and classes. However, if a user belongs to a specific school, such as School A, they should only be able to see the data for that school and its corresponding classes.&lt;/SPAN&gt;&lt;/P&gt;
&lt;P&gt;&lt;SPAN&gt;Note that the user's email ID will follow a specific format based on their school or class. For example, if they are from the Board, their user ID will be in the format username@board.com. Similarly, School A will have username@SchoolA.com, and so on.&amp;nbsp;&lt;/SPAN&gt;&lt;span class="lia-inline-image-display-wrapper lia-image-align-inline" image-alt="Hiearchy Flow Chart" style="width: 921px;"&gt;&lt;img src="https://community.qlik.com/t5/image/serverpage/image-id/163405iE342888C6976047E/image-size/large?v=v2&amp;amp;px=999" role="button" title="HiearchyFlowChart.png" alt="Hiearchy Flow Chart" /&gt;&lt;span class="lia-inline-image-caption" onclick="event.preventDefault();"&gt;Hiearchy Flow Chart&lt;/span&gt;&lt;/span&gt;&lt;span class="lia-inline-image-display-wrapper lia-image-align-inline" image-alt="List" style="width: 315px;"&gt;&lt;img src="https://community.qlik.com/t5/image/serverpage/image-id/163404iA992F94D30C68BD1/image-size/large?v=v2&amp;amp;px=999" role="button" title="List.png" alt="List" /&gt;&lt;span class="lia-inline-image-caption" onclick="event.preventDefault();"&gt;List&lt;/span&gt;&lt;/span&gt;&lt;/P&gt;</description>
    <pubDate>Thu, 04 Apr 2024 07:24:52 GMT</pubDate>
    <dc:creator>Simran9871998</dc:creator>
    <dc:date>2024-04-04T07:24:52Z</dc:date>
    <item>
      <title>How to implement the section access for Hierarchy level roles</title>
      <link>https://community.qlik.com/t5/App-Development/How-to-implement-the-section-access-for-Hierarchy-level-roles/m-p/2437717#M97078</link>
      <description>&lt;P&gt;&lt;SPAN&gt;Hi,&amp;nbsp;&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;I would like to set up section access for our data, organized into three levels: Board, School, and Class. I have attached two snapshots for reference, which show the hierarchy in both lists (Sample&amp;nbsp;file for better understanding, note we have&amp;nbsp;client data which is present in this way only to show relationships between each other) and&amp;nbsp;flowchart form. Essentially, if a user belongs to the Board Group, they should be able to see all the data for all schools and classes. However, if a user belongs to a specific school, such as School A, they should only be able to see the data for that school and its corresponding classes.&lt;/SPAN&gt;&lt;/P&gt;
&lt;P&gt;&lt;SPAN&gt;Note that the user's email ID will follow a specific format based on their school or class. For example, if they are from the Board, their user ID will be in the format username@board.com. Similarly, School A will have username@SchoolA.com, and so on.&amp;nbsp;&lt;/SPAN&gt;&lt;span class="lia-inline-image-display-wrapper lia-image-align-inline" image-alt="Hiearchy Flow Chart" style="width: 921px;"&gt;&lt;img src="https://community.qlik.com/t5/image/serverpage/image-id/163405iE342888C6976047E/image-size/large?v=v2&amp;amp;px=999" role="button" title="HiearchyFlowChart.png" alt="Hiearchy Flow Chart" /&gt;&lt;span class="lia-inline-image-caption" onclick="event.preventDefault();"&gt;Hiearchy Flow Chart&lt;/span&gt;&lt;/span&gt;&lt;span class="lia-inline-image-display-wrapper lia-image-align-inline" image-alt="List" style="width: 315px;"&gt;&lt;img src="https://community.qlik.com/t5/image/serverpage/image-id/163404iA992F94D30C68BD1/image-size/large?v=v2&amp;amp;px=999" role="button" title="List.png" alt="List" /&gt;&lt;span class="lia-inline-image-caption" onclick="event.preventDefault();"&gt;List&lt;/span&gt;&lt;/span&gt;&lt;/P&gt;</description>
      <pubDate>Thu, 04 Apr 2024 07:24:52 GMT</pubDate>
      <guid>https://community.qlik.com/t5/App-Development/How-to-implement-the-section-access-for-Hierarchy-level-roles/m-p/2437717#M97078</guid>
      <dc:creator>Simran9871998</dc:creator>
      <dc:date>2024-04-04T07:24:52Z</dc:date>
    </item>
    <item>
      <title>Re: How to implement the section access for Hierarchy level roles</title>
      <link>https://community.qlik.com/t5/App-Development/How-to-implement-the-section-access-for-Hierarchy-level-roles/m-p/2439855#M97195</link>
      <description>&lt;P&gt;&lt;A href="https://community.qlik.com/t5/Design/Authorization-using-a-Hierarchy/ba-p/1476319" target="_blank"&gt;https://community.qlik.com/t5/Design/Authorization-using-a-Hierarchy/ba-p/1476319&lt;/A&gt;&lt;/P&gt;</description>
      <pubDate>Wed, 10 Apr 2024 14:48:38 GMT</pubDate>
      <guid>https://community.qlik.com/t5/App-Development/How-to-implement-the-section-access-for-Hierarchy-level-roles/m-p/2439855#M97195</guid>
      <dc:creator>hic</dc:creator>
      <dc:date>2024-04-10T14:48:38Z</dc:date>
    </item>
  </channel>
</rss>

