With Qlik Sense, you should care more about building dashboards with live data. This means you can build amazing self-service applications in your build node, which is connected to the production node through a master central node. This brings a whole new meaning the old IT approach, which is usually very static and slow to change. 

Developers can create applications under "My Work" space. Anything created in this section will be visible only to the developer. Once the application is ready to be promoted, the administrator can create a copy by duplicating the application and deploying it to a specific stream within the same build note. This stream can be used by testers or selected business users to test the application before promoting it to a stream in the production node.

You can configure who has access to each stream using the Security Rules described in Chapter 3, Security Rules: Attribute Based Access Control. 

The superuser can also help develop applications. The best approach here would be to limit the superuser to visualizations, measures, and dimensions created in the master items. By doing so, you make sure to have proper control over what is used in the applications and ensure all elements are previously tested.

Collaboration puts the power in the hands of the business. The business will promote the use of Qlik Sense and the use of the applications. Whatever is created by a superuser will not replace anything in the published application. Instead, it will appear in a different area of the Hub. End users can have access to the guided dashboard but they can also access the more flexible dashboards created by the superuser. 

This defines a whole new meaning to the Qlik Sense consultant role as they will now spend more time training end users and superusers on how to best use Qlik Sense as well as answering any questions related to the tool. The Qlik Sense developer will also be the one who creates and maintains the data model along with the master items.