What is Gitoqlok
Gitoqlok is a Chrome and Edge browser extension that adds Git version control and a developer toolkit to Qlik Sense. It works directly in the Qlik user interface: you open an app in the browser, click the Gitoqlok icon and commit, compare, roll back or import — without any third-party servers.
How it works
Gitoqlok runs inside your browser tab as an extension. It talks to Qlik through the same session you are already logged into and talks to your Git provider through its REST API with a token you supply.
- The extension connects to the open app through the Qlik Engine API (the same WebSocket the Qlik client uses) and serializes the app into JSON: sheets, master items, variables, bookmarks, stories, the load script and app properties.
- The JSON files are committed to a Git repository on GitHub, GitLab, Bitbucket Cloud, Bitbucket Server, Azure DevOps, AWS CodeCommit or Gitea. One app is linked to one repository; copies of the app can be linked to branches of the same repository.
- Any committed version can be read back from Git and applied to the app (roll back, update from a branch, import selected sheets into another app).
Nothing leaves your browser except the calls to your own Qlik server or tenant and to your own Git provider. Tokens are stored encrypted in the local extension storage. See Security and Privacy.
What gets versioned
| Repository content | Source in the app |
|---|---|
| Load script | Each script section as a .qvs file plus the section order and the full joined script |
| Sheets and their charts | One JSON file per sheet, including every visualization on it |
| Master measures, dimensions and visualizations | One JSON file per master item |
| Variables | One JSON file per variable |
| Bookmarks | One JSON file per bookmark |
| Stories and snapshots | One JSON file per story and per snapshot |
| App properties and fields | properties.json, appprops.json, fields.json |
| Attached files (app content) | Thumbnails, images and other files uploaded to the app |
| Reload tasks and data connections (Qlik Sense Enterprise) | Optional, chosen at commit time |
| Data connections and automations (Qlik Cloud) | Optional, chosen at commit time |
| Custom theme | Stored when the app uses one |
| QVF binary | Optional, saved into a build folder on each commit |
The exact folder layout is described in Repository File Structure.
Supported platforms
| Platform | Support |
|---|---|
| Qlik Cloud (SaaS) | Full support, including standalone Scripts and Automations |
| Qlik Sense Enterprise on Windows (client-managed) | Full support, plus QMC-related tools: Reload Tasks, Environment Migration, Security Rules Manager |
| Qlik Sense Desktop | Not supported (no browser session) |
| Browser | Google Chrome and Microsoft Edge (Chromium), latest versions |
Some tools exist on one platform only. Every feature page in this documentation starts with an availability badge, and the full list is in Feature Availability.
Community and support
Join the Gitoqlok Slack community to exchange ideas and talk to the Customer Success and Development teams. Support tickets can be submitted from the Options page → Support.
Where to go next
- Installation
- Quick Start — connect a Git server and make the first commit in five minutes
- User Interface Overview — popup, side panel, Qlik Helper and the extension icon menu
- Version Control for Qlik Sense and Qlik Cloud — the options compared, and where Gitoqlok fits
