It’s estimated companies churn 52% per annum in the USA, 22% in/out and 30% internal role changes within organizations which leads to quite a lot of time to manage data security on an application and user level.

Qlik Section Access (SA) is a very code based and manual method to manage security, users and access to data within Qlik applications. Qlik SA is generally managed as code within some protected sheets or writeback table type solutions. These solutions are very manual and static to manage and sometime complex to understand.

As change is constant and user churn is a reality this work, generally performed by developers, soon become very expensive to maintain. Developer’s time is better utilized developing and Section Access work is seen as maintenance thus not always the first thing developers attend to which impacts time to insights.

Since Section Access is seldom self-service it still requires a business stakeholder, possibly a service desk agent and a developer to attend to one person joining or leaving a business unit or the company. These people generally have access to multiple application thus compounding the work required per change event having to change the SA in multiple applications.

The challenge with SA is security and application logic changes and so does user access methods and reduction logic. Section Access is static in a way but can and does change with every change event and when you have data reductions these changes take more time and requires more testing.