Easily Switching Qlik Cloud App Ownership for Team Collaboration in Shared Spaces
Many Qlik developers hit the same wall when working as a team: to hand an app to another developer, you have to change its owner. In Qlik Cloud that means a trip through the Management Console, hunting for the app, reassigning ownership, and repeating it every time the work needs to move. This ownership friction turns simple handoffs into a chore and quietly blocks smooth multi-developer workflows in shared spaces.
The manual way: ownership as a bottleneck
Say two people need to work on the same dashboard. One owns it, the other can only look. To actually contribute, the second developer either waits for an ownership switch or duplicates the app into their own space. Now there are two copies drifting apart, and someone has to manually re-apply changes back into the "real" app.
Each ownership change is a manual QMC/console action. Do it a few times a week across several apps and it adds up: forgotten reassignments, apps stuck under the wrong person, and no record of who changed what. Collaboration ends up organized around who happens to own the file rather than around the work itself.
Collaboration that isn't tied to a single owner
Gitoqlok brings Git version control, collaboration and change history to Qlik Sense and Power BI — right inside your browser. Try Gitoqlok Free
The cleaner model is the one software teams already use: everyone works from a shared repository, on their own branch, and merges finished work back. No one has to "hold" the app for others to contribute. Changes travel through commits, not through ownership reassignments, and every edit is attributed and reversible.
TIP
A practical habit: give each developer their own branch (e.g. by username) and merge through Pull Requests. Work stays isolated until it's ready, so two people editing the same app never overwrite each other.
The Gitoqlok way
With Gitoqlok's collaborative Git workflow for Qlik Sense, several developers version the same app and script to GitHub, GitLab, Bitbucket or Azure, each committing on their own branch and merging via Pull Requests. To pull a teammate's work into your own copy, use Connect to existing repository and fetch the latest commit — no Management Console ownership switch required. Full change history and rollback come along for free.
You still own your apps in Qlik as usual. Gitoqlok simply removes ownership as the gate for collaboration: work flows through commits, branches and merges, so a team can build the same dashboard together without passing a single owner flag back and forth.