Who Created Each Sheet? Tracking Qlik Object Authorship and Ownership
Open a Qlik Sense managed space and you can see who owns an app — but not who built which sheet, who added a particular bookmark, or who last touched a KPI. Many Qlik developers want that per-object visibility, and they want a way to keep working when a colleague leaves the team. Today, a departing user's objects sit there with no clear author and no obvious way to hand them over, which quietly erodes team collaboration.
How teams track this today
Without version control, authorship lives in people's heads. You ask around in Slack, dig through email, or open the app and guess from naming conventions. Qlik shows a single app owner, so a sheet built by an analyst who left months ago still reads as owned by whoever now holds the app — the real creator is invisible.
It gets worse at handover. When a user leaves the tenant, their private copies and in-progress work become orphaned: there is no record of what they changed, no per-sheet history, and no safe way to pick up where they stopped. Reassigning ownership in a managed space is an admin chore that carries none of the context about who did what.
Gitoqlok brings Git version control, collaboration and change history to Qlik Sense and Power BI — right inside your browser. Try Gitoqlok Free
How Gitoqlok records authorship in Git
Gitoqlok serializes every app object into its own file in a Git repository: one JSON per sheet under objects/sheets/<id>.json, one JSON per bookmark, one per master item. Every time someone clicks Save changes on the Local Changes tab, the commit is stamped with their Git identity and message. The result is a per-file audit trail: for any sheet or bookmark, the Git history answers who created it, who changed it, and when — down to the individual object.
That authorship is visible right inside Qlik, too. Open a sheet, click the green Gitoqlok button and choose Time Machine: the timeline separates each contributor's commits into their own swimlane, so you see at a glance who touched the sheet and when. And nothing is orphaned when people move on — because every version lives in the repo, a team lead can select any commit and use Deploy from Git to rebuild a departed colleague's work into a fresh app they own, keeping the full history intact.
Be honest about the boundary: Gitoqlok does not rewrite Qlik's native owner field for you. What it gives you is the missing record — traceable authorship per object and a safe path to recover and reassign work — so a user leaving no longer means lost context or untraceable sheets.