article Qlik Cloud Analytics: Can the owner of orphaned Apps be changed after the owner is deleted? in Official Support Articles

Qlik Cloud Analytics: Can the owner of orphaned Apps be changed after the owner is deleted?

Nobuaki_T — Fri, 27 Sep 2024 13:02:48 GMT

When a user is deleted, any spaces, apps, scripts, and data connections they own will remain in the tenant without an owner. To prevent orphaned records, reassign ownership of these assets before deleting the user. Source: Reassigning ownership of spaces and resources (Qlik Cloud Documentation)

But even if the app is considered an Orphaned App, the owner can be changed in the Qlik Cloud Analytics Administration Console:

Open Qlik Cloud and open the menu
Access the Administration menu
Go to Content
Select the Apps tab
Filter by Deleted User in the Owner column

Apps owned by Deleted Users will be listed.
Click the ... (ellipses) menu
Select Change Owner and change the ownership of the app

Environment

Qlik Cloud Analytics

Re: Qlik Cloud Analytics: Can the owner of orphaned Apps be changed after the owner is deleted?

Ken_T — Wed, 04 Dec 2024 19:58:44 GMT

if an app in a personal or shared space had some private sheets, will these steps recover/change ownership of those private sheets? thank you!

Re: Qlik Cloud Analytics: Can the owner of orphaned Apps be changed after the owner is deleted?

Frank_S — Wed, 04 Dec 2024 22:59:27 GMT

Hello,

Please check the following thread regarding your specific question.

https://community.qlik.com/t5/Move-to-SaaS/Anyone-ever-found-a-way-to-recover-private-sheets-that-belong-to/m-p/2496088#M2221

Kind regards..

Re: Qlik Cloud Analytics: Can the owner of orphaned Apps be changed after the owner is deleted?

Ken_T — Wed, 04 Dec 2024 23:00:09 GMT

that idea is closed and archived. I cannot link to it, but I have created a new product enhancement request / idea specifically for this issue. allow tenant admins to change owners of all private sheets #442217 I wish it was possible for all community users to be able to see and vote on ideas

Re: Qlik Cloud Analytics: Can the owner of orphaned Apps be changed after the owner is deleted?

chriscammers — Thu, 05 Dec 2024 18:47:32 GMT

I have a somewhat crazy suggestion but it would provide a work-around for your problem.

What I am going to share came from a project we did for a company who merged with another company and we needed to change the identity provider and assign all the users in saas to new email addresses. After a ton of testing we did the conversion by taking the following steps

Add the new Identity provider but don't activate it.
Use an Automation to update the users' email addresses to match the address they will use from the new identity provider
Activate the new IDP and have the users login

When the users logged in with the new idp the identity provider matched the email address and updated thte user information using the info from the new IDP. Finally all the content the user had under the old email was now available under the new one.

In your situation if you have a user who leaves or whatever you could in the same way update the email address of the user who owns the content you want to recover and then login using the new email address. Clearly you'd have to have a user profile that is not currently in your tenant but that would be easier than trying to hack the thing to transfer the contents.

You can do all this with Qlik Automations or postman using the api.

Best of luck.

Chris

Re: Qlik Cloud Analytics: Can the owner of orphaned Apps be changed after the owner is deleted?

chriscammers — Mon, 24 Aug 2026 19:50:15 GMT

After a long time I recieved a direct message regarding the approach we used to update the user email address using an automation. We used the Qlik Raw API Request block on the user/{id} endpoint to send a patch request with a body that looks like this.

We set up a JSON input file with the old and new email address mapping and then looped over the input searching for and updating the emails.

More recently we did a similar function to assign custom groups to users who are provisioned but not yet active, this is a limitation in the management console UI.