Skip to main content
Announcements
Join us at Qlik Connect for 3 magical days of learning, networking,and inspiration! REGISTER TODAY and save!
cancel
Showing results for 
Search instead for 
Did you mean: 
HombreM
Contributor II
Contributor II

Handling app support like reloads, when you can't change the owner

Hi there,

We are looking to deploy existing Qlikview/QlikSense apps and build new QlikSaaS apps on QlikCloud.

We currently have a large third party team supporting Qlik. They have access to QMCs via a specific AD group, so they are able to reload task chains/apps if they fail. They also have access to the servers/ folder structures, so they can make fixes to apps and can then deploy new versions.

However, we have learnt in QlikSaaS, the owner of a published dashboard cannot be changed and is alao single user. As only this owner can start a reload and overwrite a published app (we think) ... We wondered how an external support team can continue to do reloads and make changes as part of incidents?

Is any one else in this situation? Or are there some different approaches you are taking to support and maintenance?

Thank you!

Labels (1)
  • Cloud

1 Solution

Accepted Solutions
Daniele_Purrone
Support
Support

Hi @HombreM ,

I think you have incorrect information: owner of apps can, of course, be changed.

Also, by assigning permissions on spaces, you can have different users or groups performing reloads.

Here's an example for shared spaces and professional users:

Daniele_Purrone_0-1715089956968.png

In managed spaces, you will need a "can manage" role:

Daniele_Purrone_1-1715090111055.png

 

As you can see, anyone with a "Can Edit" role, or above, can perform reloads.

For more details, check:
https://help.qlik.com/en-US/cloud-services/Subsystems/Hub/Content/Sense_Hub/Spaces/permissions-share... 

and

https://help.qlik.com/en-US/cloud-services/Subsystems/Hub/Content/Sense_Hub/Spaces/permissions-manag... 

Please Note: if you are talking about apps that are distributed from client managed installation to your tenant, then the reloads need to be run on the client managed installation, not on the cloud.
In the hybrid solution, the "managing" server is always the Windows installation, not the cloud one.

Daniele - Principal Technical Support Engineer & SaaS Support Coordinator at Qlik
If a post helps to resolve your issue, please accept it as a Solution.

View solution in original post

2 Replies
Daniele_Purrone
Support
Support

Hi @HombreM ,

I think you have incorrect information: owner of apps can, of course, be changed.

Also, by assigning permissions on spaces, you can have different users or groups performing reloads.

Here's an example for shared spaces and professional users:

Daniele_Purrone_0-1715089956968.png

In managed spaces, you will need a "can manage" role:

Daniele_Purrone_1-1715090111055.png

 

As you can see, anyone with a "Can Edit" role, or above, can perform reloads.

For more details, check:
https://help.qlik.com/en-US/cloud-services/Subsystems/Hub/Content/Sense_Hub/Spaces/permissions-share... 

and

https://help.qlik.com/en-US/cloud-services/Subsystems/Hub/Content/Sense_Hub/Spaces/permissions-manag... 

Please Note: if you are talking about apps that are distributed from client managed installation to your tenant, then the reloads need to be run on the client managed installation, not on the cloud.
In the hybrid solution, the "managing" server is always the Windows installation, not the cloud one.

Daniele - Principal Technical Support Engineer & SaaS Support Coordinator at Qlik
If a post helps to resolve your issue, please accept it as a Solution.
Tami
Contributor III
Contributor III

Hi,

The owner of applications can be changed when you set up permissions.
In our cloud deployment, we created a space for shared development so designated users can modify. We republish any changes to the application from the folder.
Reloads ownership can be changed but become disabled when changing owners. Remember to enable reloads.
The owners is not the only one that can reload an application. We have a separate reload block chain created for manual reloads that is assigned to our company admin and not the consulting group.