A data architect implements Section Access on an app to reduce the data for each user when the user logs in. Each user is allowed to see their…

Scheduled reloads in a Qlik Sense environment are executed by the Qlik Sense service account (e.g., INTERNAL\sascheduler), not by the individual developer's account. When Section Access is implemented, the script's execution context is subject to these security rules. For the reload to succeed, the service account must be explicitly listed in the Section Access table, typically with ADMIN level access. This grants the service the necessary permissions to load the entire dataset. If the service account is not included, it is denied access to the data, causing the script execution and the scheduled reload to fail.

A. The ACCESS column name is case-insensitive in the Qlik load script, so using lowercase would not cause a reload failure.

C. An incorrectly spelled user name would prevent that specific user from accessing the app, but it would not cause the entire scheduled reload process to fail.

D. The data architect's personal rights are irrelevant for a scheduled reload, which is executed by the system's service account, not the architect's user profile.

1. Qlik Sense Enterprise on Windows Help, "Managing data security with Section Access": In the section discussing reloads, the documentation states: "The user identity that is used to run the scheduled reloads of an app with section access must have ADMIN privileges in the section access table of the app. If the user identity is not an ADMIN, the reload will fail." This directly supports the conclusion that the service account must be included. (Accessed under Administering Qlik Sense Enterprise on Windows > Managing apps > Managing data security with Section Access).

2. Qlik Sense Enterprise on Windows Help, "Tutorial - Using section access": This tutorial guides users through implementation and highlights common requirements. It implicitly and explicitly notes that the user reloading the data must have access. For scheduled tasks, this user is the service account. The failure described in the question is a classic outcome of omitting the service account from the security table. (Accessed under Creating visualizations and apps > Loading and managing data > Managing data security with Section Access).