define your reduction on the lowest possible level. that's usually the easiest thing to do:
if you have 3 Locations:
Region, Level1, Level2
you should define the access like this if you want Arun to have access to all the Sea Level1:
It's the easiest and the most overviewable, especially because the * may not work if you don't list all the possible values in your access table.
If I have n no. of list, Should I define all possible members? And If I kept empty instead of *, I couldn't access the app
My scenario is like Director can see all employees details, but employees can view their own data as well region level.
Consider Arun is the Director, he can view all employees data where rest of them can view their own data and their below level employee's data
AP, Ram, Sam
AP, Arun, *
AP, Kumar, Ravi
yes, again, section access is not a hierarchy table, it's linking the user to what she/he is allowed to see. (1 to 1, but a user may appear several times in the table)
and yes, you should list all the possible values for your lowest level. if you don't have the list, you may be able to generate it in your script?