Connecting Qlik to a Git Repo with Integrated Authentication for Version Control
A common request among Qlik developers: let the tool authenticate to a Git repository — say, an Azure DevOps repo behind Azure AD — using integrated credentials, instead of pasting a username and password every time you want to version control an app. It sounds small, but the friction adds up. When authentication is awkward, people commit less, and the whole point of Git for Qlik Sense — history, rollback, collaboration — quietly erodes.
The manual way: fighting the plumbing before you commit
Getting Qlik and a Git repo talking natively is rarely a one-click affair. You wire up a connection, then hit the credential wall: basic auth prompts, expiring passwords, or a repo that only accepts your organization's integrated Azure AD sign-in. If your tooling can't hand off to that sign-in, you fall back to manually managing usernames and passwords for a repository your company already authenticates you to.
From there it gets more manual still. You export or serialize the app somewhere, figure out how objects map to files, push them by hand, and repeat the credential dance on every developer's machine. Each new team member is another setup guide, another token to store safely, another chance for a mismatched configuration to break the connection mid-commit. The version control you wanted becomes a side project.
Gitoqlok brings Git version control, collaboration and change history to Qlik Sense and Power BI — right inside your browser. Try Gitoqlok Free
What you actually want
The goal is simple: open a Qlik app, connect it to your repo, commit as you work, and roll back when needed — without babysitting authentication. Credentials should be entered once, stored securely, and reused. The Git provider your organization already standardized on (GitHub, GitLab, Bitbucket, or Azure DevOps) should just work, so the team can branch, review, and merge Qlik changes like any other codebase.
The Gitoqlok way
Gitoqlok is a Chrome extension that connects your Qlik Sense apps and load scripts to Git directly from the browser. You configure a Git Server profile once with a personal access token — including Azure DevOps and other providers — and Gitoqlok reuses it for every repository and commit. Tokens are stored locally in the browser and encrypted with AES, so you set authentication up once instead of retyping credentials each session.
After that, versioning is where it belongs — inside Qlik. Create a repository, use Local Changes to commit sheets, script, bookmarks and more, and Update to roll back to any previous version. For teams, Applications Manager spins up repositories for many apps at once, so the whole environment moves onto version control without the per-app credential grind.