3 Replies Latest reply: Jun 4, 2012 3:51 PM by Logesh Jayaraman RSS

    Section Access

    Logesh Jayaraman

      Hi,

       

      1. Would like to reduce the data based on the user group and we have done it sucessfully using the NT name in the section access.

      2. Now at Accesspoint we want to restrict the document will be visible only to the users who has the access to it. How to do it?

      3. Else is there any option to generate the URL for each user based on the data security so that rather providing the access to the Accesspoint we can give the link to the user directly.

       

      Please suggest . Thanks

        • Section Access
          Bill Britt

          Starting in version 10 if a user does not have rights to the document in section access then the user will not see the document in the AccessPoint..

          • Section Access
            Miguel Angel Baeyens de Arce

            Hi,

             

            As long as QlikView relies security on the file system, make sure that in the Settings menu, Document Properties, Server tab, the "Filter AccessPoint Document List based on Section Access" is checked. So if either the user is not in a group with NTFS permissions on the file or it does not belong to a member of the group allowed in the NTNAME, the user shouldn't be able to see the document, even if he's allowed to get to the AccessPoint.

             

            When security works with NTFS, there is no way to create that "customized" URL for each user. You should use / build a Single Sign On, and it might not be worth it, specially if the solution above works.

             

            Hope that helps.

             

            Miguel

              • Section Access
                Logesh Jayaraman

                Thanks Bill &Miguel,

                 

                One more question to you , what you said is irrespective of the Qlikview server authentication either NTFS or DMS.

                 

                Miguel can you please let me know You should use / build a Single Sign On, and it might not be worth it, specially if the solution above works. the way how to do this.