Skip to main content
Qlik Introduces a New Era of Visualization! READ ALL ABOUT IT
Showing results for 
Search instead for 
Did you mean: 
Contributor III
Contributor III

Best Practice/ Docs: QlikSense Organisation and Structure


after we did first progress technically with QlikSense we are now facing some issues by building an internal organization that allows us to scale the usage of the system while still being able to govern the system with a small team.

It would be great, if you could share your organizational structure with some basic roles and responsibilities. Furthermore it would be great if you could share how you are using streams and what is your definition of it (when to create a new one, what shall be the content...)

Maybe there are also some docs available.


I am grateful for any hints!

Labels (3)
1 Reply
Contributor III
Contributor III

Some remarks on our company:

  • we have roughly 10.000 employees
  • we are supplier for complex metal and hybrid structures in body-in-white, crash management systems, chassis applications and cross car beam
  • we have three nodes (test/ development & data aggregation/ App Usage)

Here is our current approach:

1. IT

Currently we have 1.5 - 2 FTEs for QlikSense. IT shall be responsible for the system itself:

  • Maintenance of the System
  • Update of the System
  • Data Connections
  • Integration of Jobs for Reload
  • Support business Units in case of issues

2. Business Unit

  • each business unit shall have one "QlikSense Responsible" that is able to publish/ republish apps
  • this person shall manage all activities within the business unit and has advanced access to functions in QlikSense
  • each business unit can have also "QlikSense Developers" that are allowed to create apps/ sheets
  • for each app we have "key users". They are not able to create apps or sheets. They are "just" trained on the purpose and usage of the app. They shall support and train users on first level

For us it is very hard to find a way that supports the self service approach but suppresses chaos on our system.

We are also struggling on definition of streams. First of all we could have one Stream for each business unit since there is a clear definition of responsible persons. But on the other hand we have several apps, that are cross functional, so users from different streams will access them.