Skip to main content
Woohoo! Qlik Community has won “Best in Class Community” in the 2024 Khoros Kudos awards!
Announcements
Nov. 20th, Qlik Insider - Lakehouses: Driving the Future of Data & AI - PICK A SESSION
cancel
Showing results for 
Search instead for 
Did you mean: 
alexis
Partner - Specialist
Partner - Specialist

Section Access question

Hi All

I'm trying to implement section access in Qlik Sense - last time I even looked at Section Access was some years ago.

I want to implement a mechanism where I can give certain users access to all the reduction values even those not listed in the section access - let me illustrate with an example..

SECTION ACCESS;

LOAD * Inline [

ACCESS, USERID, PRODUCT

ADMIN, ADMIN1, *

USER, MANAGER1, *

USER, USER1, A

USER, USER2, B

];

SECTION APPLICATION;

LOAD * Inline [

PRODUCT, Data

A,2

A,3

B,4

B,3

C,5

C,4

];

I am guessing here that both the ADMIN and the MANAGER1 will have access to PRODUCT values A and B but not C as this (the value C) is not used in any of the reduction statements for the rest of the users.

I saw somewhere online (but it was from 2014 and referred to QlikView) that simply adding a reduction value that is not a wildcard (i.e. *) and does not exist in the reduction field (PRODUCT in this case) has the effect that I want which is to give a user access to all values irrespective of whether they are used in the reduction definition or not.

Questions:

1) Would changing:

USER, MANAGER1, *

to

USER, MANAGER1, <ALL>

have the effect that I want for MANAGER1?


2) What happens to ADMIN after the above - will she/he also see everything as they too now will see the <ALL> reduction?

If the above is not going to work how have people implemented "Managerial" access to dynamic fields (used in reduction for non-managerial users) that have too many values to allow manual input of every combination that exists in the data?

Thanks in advance

Alexis

1 Solution

Accepted Solutions
vitaliichupryna
Creator III
Creator III

Hi Alexis,

1) If you just change * to <ALL> Manager will not be able to open the application.

2) Will not be able to see everything because it doesn't work for manager.

You should create authorization bridge, see attached example.

Thanks,

Vitalii

View solution in original post

2 Replies
vitaliichupryna
Creator III
Creator III

Hi Alexis,

1) If you just change * to <ALL> Manager will not be able to open the application.

2) Will not be able to see everything because it doesn't work for manager.

You should create authorization bridge, see attached example.

Thanks,

Vitalii

alexis
Partner - Specialist
Partner - Specialist
Author

Hi there Vitalii

Your approach works fine (I just added a DISTINCT statement in the LOAD statement for efficiency), so I will award the "Correct Answer" - I am still intrigued by the Qlik video from Qlik Support entitled Section Access Best Practises - see  https://youtu.be/Cq4QzR9s7AA ) which seems to support my suggested approach - care to comment once y...

T‌hanks

Alexis