The Section Access Challenge

Change is constant

User churn within organisations has a major impact on security and data management processes within an organisation and systems. Qlik is no different in this regard as your data for analytics is hosted within your Qlik Applications (Apps) and requires management to ensure the correct people can access and explore only the correct data. This data management method is called Section Access Management in Qlik.

Section Access Management is generally performed by Qlik developers as in a Qlik App it is implemented as script/code thus not something a business user or stakeholder with access requirements can self-service with as business people generally don’t script or code Qlik Apps. Once Section Access is activated on a Qlik Application every churn event related to that application requires someone to make changes to the Section Access of that App. The real multiplier challenge is one churn event generally have multiple changes across multiple Applications as one person can have access to many Applications.

Change examples are a person joins a company and is provided access to their Apps. That person changes their role and requires changes to their existing applications to remove them from accessing the data and applying their access to their newly required data access within their new role.

The is much more user churn, Apps and data changes than developers and this generally leads to bottlenecks. File and write-back table type solutions supports the possibility of self-service but does not automate the process.

We have seen a global increase in regulatory requirements on data, data access, personal data protection and general data management control within organizations and we don’t expect this to decline anytime soon.