Back Up Qlik Sense Apps with Section Access via CLI or Automation
Many Qlik developers want a way to back up Qlik Sense apps that use section access through the CLI or an automation, and keep hitting a wall. The apps that most need reliable backups — the governed, row-level-secured ones — are exactly the ones that resist scripted export. So they get left out of the backup routine, and a single bad reload or deleted app becomes unrecoverable.
Why CLI and automation choke on section access
A normal app exports cleanly with qlik-cli or a Qlik Application Automation. Add section access and the calling identity suddenly matters: the service account or token running your automation may not be listed in the security table, so it either can't open the app or exports a data-restricted copy. Admin overrides exist, but wiring them into an unattended job is fragile, and a mistake risks exporting sensitive rows to the wrong place.
The manual fallback — and what it costs
Gitoqlok brings Git version control, collaboration and change history to Qlik Sense and Power BI — right inside your browser. Try Gitoqlok Free
The usual workaround is manual: an admin opens the QMC, exports each governed app to a .qvf by hand, and drops the files on a share. It works once. It does not scale to dozens of apps, it captures no history (only the latest full copy), and it tells you nothing about what changed between two versions. Miss a week and the newest backup is already stale. Restoring means re-importing a whole app, not recovering the one sheet or script section that broke.
You also lose granularity. A .qvf on a network drive is one opaque blob. When a load script edit quietly breaks a reload, you want to see the diff and roll back just that change — not restore the entire app from last month and redo everyone's work since.
The Gitoqlok way
Gitoqlok runs in your browser using your existing Qlik session, so it inherits your access rights and reaches section-access apps without a separate service account. Each commit versions the load script, app objects, bookmarks and static files into Git as JSON, and you can enable "save a QVF file with every commit" to export the full .qvf into a build folder on every save — giving you both readable history and a restorable file, with rollback to any previous version.
TIP
Because backups live in Git, restore is selective: pick a commit, hit Update, and recover a single script section or sheet instead of overwriting the whole governed app.