Section Access: Are "dummy" entries necessary?

[daveatkins]

Following very old examples of section access, I was under the impression that when the reduction is "*" this only matches the specified reductions in the section access table.

For example:

ACCESS, USER, REDUCTION

USER, DA123, *

USER, AB456, NORTH

USER, CEF789, SOUTH

if the data contains "REDUCTION" value of "WEST" then DA123 will not see it, unless I add a row:

DUMMY, DUMMY, WEST

Does this hold true for admin users?

ADMIN, DA123, *

USER, AB456, NORTH

USER, CEf789, NORTH

Does DA123 now see WEST, or is a dummy still required?

Hopefully...the answer is no. Otherwise I am not sure what the purpose of the ADMIN role is.

[Chanty4u · Accepted solution]

Hi

the purpose of the ADMIN role is to provide full access to all data without the need for additional dummy entries. You should not need dummy entries for ADMIN users.

[daveatkins]

A developer pointed out to me that this is only true for QlikSENSE. On QlikView, the ADMIN role is not applicable and dummy rows must be used.

https://help.qlik.com/en-US/qlikview/April2020/Subsystems/Client/Content/QV_QlikView/Security.htm

This explains my misunderstanding...following our practices from QlikView, I assumed the dummy rows were necessary.