Help for correct in Section Access use.

MigueldelCampo — Tue, 27 Jan 2026 10:45:26 GMT

Hello guys!,I am currently facing an issue with implementing "Section Access" in my Qlik Cloud application using a CSV file. Despite following several references and guidelines *, **, I am unable to get the application to recognize the user-related access when reloading.Here are the specifics of my situation:

Data Source: I am loading Section Access data from a CSV file.
Expected Behavior: The application should restrict data visibility based on the user logged in, according to the mappings defined in the CSV.
Current Behavior: When I reload the application, it does not apply the intended user restrictions.

From my understanding, the following points are crucial for Section Access to work correctly:

Field Names and Values: All field names and values in the Section Access table must be in uppercase.
User Identification: The USERID used in Section Access should match exactly with how users are identified in Qlik Cloud, particularly regarding any identity provider settings.
Script Structure: The Section Access script must be properly structured within the load script, initiated by Section Access; followed by Section Application;.

Could anyone provide insights or share their experiences regarding similar issues? Any help or guidance would be greatly appreciated!

*Managing data security with Section Access | Qlik Cloud Help

**A Primer on Section Access - Qlik Community - 1465766

Re: Help for correct in Section Access use.

rubenmarin — Sat, 26 Oct 2024 07:03:25 GMT

Hi, when you say "it does not apply the intended user restrictions." can you be more explicit? it doesn't filters any values, it filters unwated values, users don't have access...

You can also comment the Section Access; line and check what happens when you select an USERID. Are the expected values filtered in this case?

topic Help for correct in Section Access use. in Move to Qlik Cloud Analytics

Help for correct in Section Access use.

Re: Help for correct in Section Access use.