Section access

[Qliksense_77]

Hi

I have an app that everyone should be able to access. There are too many potential users to list them all.

There is one field with confidential information. Lets call the field for "Customer-ID".

The field  "Customer-ID" should be hidden from almost all of the users. But there are a few users (managers) that should be able to see the field "Customer-ID" for their own departments.

How to set up a section access model, where manager A only can see "Customer-ID" for department A.

And mangager B can only see "Customer-ID" for department B and so on.

Anybody that can help ?

[mpc]

Hi, 

Maybe the OMIT keyword can help you ? It's will hide field based on your CUSTOMER-ID
For instance this post may help you: Handling Omitted fields in Qlik Sense (Section Access) - Ometis

Best

[marcus_sommer · Accepted solution]

Most authorizations, including section access, are following a white-list logic. This means nothing is allowed unless it's explicitly listed. Therefore you will need to list everything what's required - whereby it's not mandatory necessary to do it manually else it could be done programmatically.

Ideally the authorizations are read from the active directory or a hierarchy from HR department or similar suitable sources but also with own loop/join-approaches against some minimized manual list it's possible to create large authorization-hierarchies.