17 Replies Latest reply: Feb 16, 2018 12:24 AM by Kaushik Solanki

restricting user's access

Baarathi V Feb 15, 2018 5:31 AM

How can restrict data access for different users in qliksense app? for example i have mentioned the below scenerio

CEO---> Project Manager--->Employee

CEO has access to view and edit all the data in the app.

Manager has access to view and edit data related to his project.

Employee has access to view data related to his project.

How to implement these restriction in qliksense?

Re: restricting user's access

Francesco Reggiani Feb 15, 2018 5:40 AM (in response to Baarathi V)

Hi Baarathi,

yuo can use Section Access for data restriction and security rule for permissions.

https://help.qlik.com/en-US/sense/September2017/Subsystems/Hub/Content/Scripting/Security/manage-security-with-section-a…

https://help.qlik.com/en-US/sense/September2017/Subsystems/ManagementConsole/Content/security-rule-editor.htm
Like Show 0 Likes (0)

Actions
- Re: restricting user's access
  
  youssef belloum Feb 15, 2018 5:43 AM (in response to Francesco Reggiani )
  
  Like Francesco said,
  
  there is DATA ACCESS and ITEMS ACCESS rights.
  
  for DATA ACCESS it is the SECTION ACCESS that you will need.
  
  but for your case, like described on your previous post, you are looking for ITEMS ACCESS RIGHTS.
  
  I'll try to give step by step how to do this later
  
  Like Show 0 Likes (0)
  
  Actions
  - Re: restricting user's access
    
    Baarathi V Feb 15, 2018 5:57 AM (in response to youssef belloum)
    
    Thank you Youssef Belloum for your response. Ya if possible give steps to do this.
    
    Like Show 0 Likes (0)
    
    Actions
    - Re: restricting user's access
      
      youssef belloum Feb 15, 2018 8:06 AM (in response to Baarathi V)
      
      Baarathi, just to make it clear
      
      On qliksense entreprise, the concept of project don't exist, there is only apps, streams, Content and other Items that you can link with security rules.
      
      so it is ok for having 3 different profiles (CEO, PM, EMPLOYEE)
      
      but you should specify what is the difference between the CEO and the PM in terms of access to resources.
      
      Like Show 0 Likes (0)
      
      Actions
      - Re: restricting user's access
        
        youssef belloum Feb 15, 2018 8:09 AM (in response to youssef belloum)
        
        one logic can be, for example:
        
        Many streams = 1 projects
        
        so, the CEO can access (view/edit) all the data of all the apps of all the streams.
        PM: can access (view/edit) all the data of all the apps of one specific stream
        
        Or the opposite.
        
        Like Show 0 Likes (0)
        
        Actions
      - Re: restricting user's access
        
        Baarathi V Feb 15, 2018 8:20 AM (in response to youssef belloum)
        
        Thank you Youssef, But here I referring to the word project it means App only, sorry it was a typo.
        
        Like Show 0 Likes (0)
        
        Actions
        
        Re: restricting user's access
        
        youssef belloum Feb 15, 2018 8:24 AM (in response to Baarathi V)
        
        Ok so here the CEO and the Project Manager have the same access rights related to data, right ?
        
        Like Show 0 Likes (0)
        
        Actions
        
        Re: restricting user's access
        
        Baarathi V Feb 15, 2018 8:26 AM (in response to youssef belloum)
        
        CEO has rights to view and edit the entire data in app. Project Manager has right to view and edit a certain part of data in app.
        
        Like Show 0 Likes (0)
        
        Actions
        
        Re: restricting user's access
        
        youssef belloum Feb 15, 2018 8:45 AM (in response to Baarathi V)
        
        I don't think there is such level of details on the security rules...
        
        If a user have access to adit data on certain app/stream/ he can edit all the data inside. (according to my knowledge)
        
        Maybe some experts can take a look here kaushik.solanki mto
        
        Like Show 0 Likes (0)
        
        Actions
        
        Re: restricting user's access
        
        Baarathi V Feb 15, 2018 8:51 AM (in response to youssef belloum)
        
        Thank You Youssef belloum for helping me out. I hope i would get a solution from kaushik.solanki or mto.
        
        Like Show 0 Likes (0)
        
        Actions
        
        Re: restricting user's access
        
        Michael Tarallo Feb 15, 2018 8:51 AM (in response to youssef belloum)
        
        Hi Guys - there are security rules and settings to control actions and resources and then there are data rules via section access (Dynamic Data Reduction) to control what rows and columns are viewed when creating / running a report. There are also certain predefined ROLES (that can be created as custom) - to control who can create and edit apps and who can view them, So before we continue, I'd like to distinguish specifically the users and their desired actions. Let's not use the term EDIT DATA - as data is only accessed via fields to create visualizations, or it is defined to create master items. I don't think anyone is actually EDITING the data - you mean editing vs. viewing the apps I am assuming.
        
        Once we have these down - we can determine the best approach - but most likely will be a combination of defining roles, setting up security rules to control data CONNECTION access and setting Section Access via (Script) to control who sees what fields and rows.
        
        Let us know
        
        Regards,
        
        Mike T
        Qlik
        
        Like Show 1 Like (1)
        
        Actions
        
        Re: restricting user's access
        
        youssef belloum Feb 15, 2018 9:01 AM (in response to Michael Tarallo )
        
        mto
        
        That's what I'm trying to understand also before going to step by step...
        
        For me (personal opinion), If it was me that created this thread I would have used the word Edit data, it would just mean for me that the user can access the script to Modify/reload it.
        
        hope it is not completely wrong..
        
        Like Show 1 Like (1)
        
        Actions
        
        Re: restricting user's access
        
        Michael Tarallo Feb 15, 2018 9:04 AM (in response to youssef belloum)
        
        Hi Youssef - nope not wrong - just semantics is all - to me editing data - is actually changing the underlying data values in a data source or table.
        
        Editing the LOAD SCRIPT would be the correct way - Editing an app - is changing / modifying the app . etc.
        
        Thanks for your excellent Qlik Community support!
        
        Like Show 2 Likes (2)
        
        Actions
        
        Re: restricting user's access
        
        youssef belloum Feb 15, 2018 9:17 AM (in response to Michael Tarallo )
        
        The community is giving me much more than what I'm giving.. so it is normal
        
        Thank you for always beeing available. your knowledge is extremely appreciated
        
        Like Show 1 Like (1)
        
        Actions
        
        Re: restricting user's access
        
        Baarathi V Feb 15, 2018 9:06 AM (in response to Michael Tarallo )
        
        @Michael Tarallo , ya you are right, we cannot edit the data. Its@ all about viewing. CEO should view the entire data, project manager should view the data which is related to him.
        
        Like Show 0 Likes (0)
        
        Actions
        
        Re: restricting user's access
        
        Michael Tarallo Feb 15, 2018 9:32 AM (in response to Baarathi V)
        
        Hello Baarathi - ok then - that makes it much clearer - so this seems to be just standard section access
        
        Please review this and let us know if you have any more questions:
        
        https://help.qlik.com/en-US/sense/February2018/Subsystems/PlanningQlikSenseDeployments/Content/Deployment/Server-Securit…
        
        When applicable please mark the appropriate replies as CORRECT. This will help community members and Qlik Employees know which discussions have already been addressed and have a possible known solution. Please mark threads as HELPFUL if the provided solution is helpful to the problem, but does not necessarily solve the indicated problem. You can mark multiple threads as HELPFUL if you feel additional info is useful to others.
        
        Regards,
        Mike T
        Qlik
        
        Like Show 1 Like (1)
        
        Actions
Re: restricting user's access

Kaushik Solanki Feb 16, 2018 12:24 AM (in response to Baarathi V)

HI Baarathi,

as mto said its a clear case of section access, check the link he gave for more info.
You can also give a small search in community for section access and you will find many examples available which can help you to understand the concept in detail.

For example below link.
Tips and tricks for section access in Qlik Sense (2.0+)

Thanks youssefbelloum to tagging me in this post.

Regards,
Kaushik Solanki
Like Show 1 Like (1)

Actions

Go to original post