Multi Layered Section Access

MartijnP — Fri, 02 Apr 2021 08:29:27 GMT

Hi All,

Within my organisation we want to use Section Access.

On a REDUCTION level we have 4 hierachy levels (lets call them 1, 2, 3 and 4 with 1 being CEO and 4 being employee)

Table looks like:

ORG_STRUCTURE:

Employee - level1 - level2 - level3 - level4

Employee number - management- business unit - department - team

On a OMIT level we want a sort of profile structure, we were thinking of putting in the OMIT field something like 'Analyst' and refering to a different table in which we specify which columns should be hidden if that role is given. This would look something like:

SECTION ACCESS:

ACCESS, USERID, REDUCTION, OMITROLE

USER, OFFICE\USER, 1234 (employeenumber), Analyst

With a separate table OMITROLES:

OMITROLE, OMITGROUP

Analyst, Salary

And another separate table OMITGROUPS:

OMITGROUP, OMIT

Salary, Year_Salary

Salary, Month_Salary

1. Based on this how would you structure the REDUCTION hierarchy?

2. A User must be specified to either show their own data only, or data from multiple users depending on their role within the organization levels. A Director should only see their own departments and all personel underneith it.

3. Is it possible to refer to a different table for OMIT or REDUCTION thus creating a sort of hierarchy

4. Would this automatically create multiple rows within Qlik for OMIT fiels as a user would have only one row in section access but multiple columns being OMITTED

5. If I have 2 rows in Section Access as below, would this result that user abc will be able to see all departmental data and salary column, or would this result in only being able to see all departmental data and not the salary column?:

USER, OFFICE\abc, 123, salary

ADMIN, Office\abc, department, (null)

Thank you for your support and thinking in advance!

topic Multi Layered Section Access in App Development

Multi Layered Section Access