Skip to main content
Announcements
See what Drew Clarke has to say about the Qlik Talend Cloud launch! READ THE BLOG
cancel
Showing results for 
Search instead for 
Did you mean: 
keerthanagowsi
Contributor III
Contributor III

Table level security in Qlik sense using section access

Hi All,

I am linking 3 different tables (say Table 1, Table 2, Table 3 for example) using keep in my qliksense load editor. Now i have a requirement to restrict the data in such a way, that specific set of users should be able to see only Table 1 data and similarly specific set of users should access only Table 2 data and so on. I know about OMIT and REDUCTION, my question is, is it possible to implement Table level security using Section Access in Qlik sense? 

I have to answer my users, based on the feasible solutions that can implemented using Qliksense.

Thanks for the help and support in advance.

 

Labels (1)
2 Replies
MayilVahanan

Hi

In that case, many fields will be removed from the app.. Is it ur requirement?

If so, try like below

USER1 - can able to see both table

USER2 - can able to see only table1

USER2 - can able to see only table2

SECTION Access;
Load * Inline
[
NTNAME, ACCESS, TABLE1, TABLE2
DomainName\USER1, ADMIN, 1, 1
DomainName\USER2, USER, 1, 0
DomainName\USER3, USER, 0, 1
];

SECTION Application;

Load * Inline
[
TABLE1, TABLE2
1, 0
0, 1
1, 1
0, 0
];

LOAD *, 1 as TABLE1 INLINE [
process_id, process_name, domain_name, parameter, Definition_no, Question_definition, score gained, max_weightage
ID0034, partno34, SKILLS, POLITENESS, Defenition1, OPENING, 5, 5
ID0034, partno34, SKILLS, POLITENESS, Defenition2, BRANDING,2.5,5
ID0034, partno34, SKILLS, POLITENESS, Defenition3, DISCONNECT, 10, 10
ID0034, partno34, SKILLS, POLITENESS, Defenition4, AGGRESSIVE, 5, 5
ID0037, partno37, SKILLS, POLITENESS, Defenition1, OPENING, 5, 5
ID0037, partno37, SKILLS, POLITENESS, Defenition2, BRANDING, 5, 5
ID0037, partno37, SKILLS, POLITENESS, Defenition3, DISCONNECT, 0, 10
ID0037, partno37, SKILLS, POLITENESS, Defenition4, AGGRESSIVE, 5,5
];

 

Logs:
load *, 1 as TABLE2 inline [
logid,date
1,01.01.2023
2,01.01.2023
3,01.01.2023
4,01.02.2023
5,01.02.2023
6,02.02.2023
7,01.02.2023
8,01.02.2023
9,02.02.2023
10,02.02.2023
11,02.02.2023
12,02.01.2023
13,02.01.2023
];

Thanks & Regards, Mayil Vahanan R
Please close the thread by marking correct answer & give likes if you like the post.
keerthanagowsi
Contributor III
Contributor III
Author

Hi,

Thanks much for the reply. But my proble here is i have a link between Table 1 and Table 2 also. By applying the above logic results in circular reference.