If you don't have Publisher, you can control access by setting the Windows Security permissions on the file. This is sometimes made easier by putting the apps in separate folders so you don't have to worry about file permissions getting overlayed by folder permissions.
Once a user has been authenticated, QlikView Server typically handles authorization on its own. QlikView Server provides the choice between storing the ACL information as Windows NTFS privileges (applicable only when the user is authenticated using a Windows user identity) or by storing the ACL information in the internal repository, Document Metadata Service (DMS), in QlikView. The choice of NTFS or DMS affects the access to all documents in QlikView Server.
NTFS vs. DMS
QlikView Server can use the NTFS privileges of the Windows file system to store authorization information. When in NTFS authorization mode, QlikView Server controls access to a given QlikView document by determining if the authenticated user has NTFS privileges to the underlying QlikView document file (.qvw). This is based on the operating system privileges and Windows NTFS is used for the ACL. The privileges of the authenticated user are configured by a server administrator using standard Windows Explorer functionality via directory properties options.
As an alternative to Windows NTFS, QlikView can use its own ACL, DMS. Unlike NTFS, this allows non-Windows users and groups to be authorized to access applications and data. DMS integrates fully with the existing Directory Service Provider (for example, Active Directory, other LDAP) where Group Membership has been recorded – this is a mechanism by which QlikView Server can re-use existing enterprise accounts and group structures. The permitted users or groups are recorded in a meta file that resides next to the QlikView document, and it is managed using QMC.
NTFS is the default document authorization model, suitable when all users and groups are identified in Active Directory or locally on the QlikView Server host. The NTFS permissions may be inherited from the directory that the QlikView documents are in, or may be assigned using QlikView Publisher distribution tasks.
DMS is required when the authenticated user identity is not a Windows user account. The DMS permissions are explicitly assigned using QMC, or may be assigned using QlikView Publisher distribution tasks.
DMS is only available with QlikView Server Enterprise Edition
Try Section Access for this. There are lot of examples in Community and in Qlikview help file.
If you just want user level then use below script
LOAD * INLINE [
If you do not have Enterprise Edition and if you are having Small Business Edition then you can also use the Windows Setting to restrict use to view applications on accesspoint.
All you have to do is for each of the application, go to properties and remove the Users Group from security and add only users which should have access to that document (Application).
Once you do this, restart Qlik Services to take immediate effect.
Thank you all for your replies. We will go with section access if we can't do anything on windows level because we are not going to apply the data level security.
We are going to migrate current server to new server with DMS authentication. We will try Sébastien Fatoux recommendation.