Multiple environments in Qlik Cloud - using Spaces?
Hi all,
I'm wondering how best to set up Qlik Cloud to have Dev, QA, and Production environments.
I use separate apps for initial data extraction (into one set of QVDs), transformation (into a second set of QVDs), and user-facing apps with facts and dimensions loaded from the second set of QVDs. I set everything up in my first wide-release Qlik Cloud app to use space-aware data sources as detailed here: https://help.qlik.com/en-US/cloud-services/Subsystems/Hub/Content/Sense_Hub/Spaces/app-data-managed-...
However, now that I'm going to deploy, I'm realizing that I don't want users to be seeing the extract/transform apps, so they should be in a different space. I suppose I could change the end user apps to read from a different space, but I figured I'd ask the question here before I do that:
What are the best practices regarding data loading and apps in multiple environments on Qlik Cloud?
Hi @FlyingCheesehead the separation of app's based on the idea of production and development, is not achieved in Cloud editions as it was with the on premises client managed editions.
With Qlik Cloud this is achieved via shared and managed spaces, and the management of membership to those spaces. The implementation of security, as to who can see what. And what a user can do is achieved using Roles and Permissions.
The Qlik Cloud editions allow for very granular control of user permissions in spaces. Basically the idea is that shared spaces are where applications are developed and allow for collaboration. Managed spaces are where the applications are published and consumed.
