But my only concern in this case would if it is only one level, we can easily repeat the number of rows of each user. But for a hierarchy like Region, Group District and Location, I was wondering how many rows do we need to put if I want to add the something which is mentioned below:
Region 100 head should have access to Region 100, 200 and 300. Along with this he should also have access to Groups, districts and Location under Region 100,200 and 300.
Or if you have User IDs linked to Regions in your data model, you can turn your Section Access into a solution that is managed automatically by the data.
Do not use an INLINE table, but load your SA table from the source table that contains regions and region heads. If those fields are in separate tables, use classical QlikView script operations to JOIN them together.
If you use NTNAME in Section Access, you probably don't have Windows Accounts somewhere in your data model, and therefor the previous solution cannot be implemented in its entirety. You can still partially automate the region-head connection by creating a Section Access table that simply grants access to NTNAME rows. Add a link field with an identifier value that does exist in your data model (like First Name-Last Name in UPPER case).
In Section Application, you create again a link table containing (optiionally multiple) First Name-Last Name values and the Region IDs for which each person is the head. Whenever, an assignment changes, your QlikView document will change as well at the next reload.
