Skip to main content
Announcements
See why Qlik was named a Leader in the 2024 Gartner® Magic Quadrant™ for Data Integration Tools for the ninth year in a row: Get the report

QlikView Section Access Examples

cancel
Showing results for 
Search instead for 
Did you mean: 
Colin-Albert

QlikView Section Access Examples

Last Update:

Oct 7, 2022 9:22:04 AM

Updated By:

Sonja_Bauernfeind

Created date:

Feb 24, 2014 6:54:29 PM

Attachments

The  attached file SectionAccess.zip contains several example documents that show how Section Access can be used to restrict access to specific users and to specific data.

 

This is not a guide on how to use Section Access, but instead shows some of the common errors and how to avoid them.

 

An excellent guide to Section Access can be found here http://community.qlik.com/docs/DOC-1853

Marcus_Sommer has accumulated a comprehensive list of Section Access Resources in this document Section Access

 

These examples will require a licenced copy of QlikView to open them, so they not suitable for users with QlikView Personal Edition.

 

The example documents will ask for a username and password to open them and set the Section Access permissions. The following usernames and passwords can be used to open the documents and see the different functionality with Section Access. When changing from one user to another, you must close QlikView before you can open a document as another user.

UserID,  Password

ADMIN,  ADMIN

JOHN, JOHN

MARY,  MARY

PETER,  PETER

SIMON,  SIMON

 

You can view the load script to see how the Section Access and data is configured.

 

Section Access Example 1

This document attempt to restrict access to a list of named users, but this fails as the section access field names are not set as UPPERCASE in the script.

 

Section Access Example 2

The app is now correct and prompts for a username and password before users can access the data.

 

Examples 1 & 2 use the Basic section access data from SectionAccess.xlsx

 

Access,  UserID,  Password

USER,  USER,  USER

ADMIN,  ADMIN,  ADMIN

USER,  JOHN,  JOHN

USER,  MARY,  MARY

USER,  PETER,  PETER

ADMIN,  SIMON,  SIMON

 

Section Access Example 3

The data is restricted so users can only access the Cost Centre data as listed in the Cost Centre  column in Section Access.

Access,  UserID,  Password,  CostCentre

USER,  USER,  USER,  *

ADMIN,  ADMIN,  ADMIN,  *

USER,  JOHN,  JOHN,  A

USER,  MARY,  MARY,  B

USER,  PETER,  PETER,  C

ADMIN,  SIMON,  SIMON,  A

 

Section Access Example 4

This adds extra DUMMY rows to the section access table so the * entries can now access all cost centres.

Access,  UserID,  Password,  CostCentre

USER,  USER,  USER,  *

ADMIN,  ADMIN,  ADMIN,  *

USER,  JOHN,  JOHN,  A

USER,  MARY,  MARY,  B

USER,  PETER,  PETER,  C

ADMIN,  SIMON,  SIMON,  A

DUMMY,  DUMMY,  DUMMY,  D

DUMMY,  DUMMY,  DUMMY,  E

DUMMY,  DUMMY,  DUMMY,  F

DUMMY,  DUMMY,  DUMMY,  G

DUMMY,  DUMMY,  DUMMY,  H

 

Note – you cannot open the document as user DUMMY because DUMMY is an invalid Access value, only ADMIN and USER entries are allowed to open the document.

 

Section Access Example 5

This adds Region to the restrictions as well as CostCentre, but the restriction on Region fails as the

region fieldname is not UPPERCASE.

 

Access,  UserID,  Password,  CostCentre,  Region

USER,  USER,  USER,  *,  *

ADMIN,  ADMIN,  ADMIN,  *,  *

USER,  JOHN,  JOHN,  A,  North

USER,  MARY,  MARY,  B,  South

USER,  PETER,  PETER,  C,  East

ADMIN,  SIMON,  SIMON,  A,  North

ADMIN,  SIMON,  SIMON,  A,  East

DUMMY,  DUMMY,  DUMMY,  D,  North

DUMMY,  DUMMY,  DUMMY,  E,  South

DUMMY,  DUMMY,  DUMMY,  F,  East

DUMMY,  DUMMY,  DUMMY,  G,  West

DUMMY,  DUMMY,  DUMMY,  H

 

Section Access Example 6

The Region fieldname is uppercase, but the restriction on Region still fails as the region data is not UPPERCASE.

 

Section Access Example 7

The Region restriction now works by loading the region data into a second field named REGION_SA and forcing the data in REGION_SA to UPPERCASE.

Version3 - The Region field has been removed from the Section Access table. This fixes the error identified by kanhomcake (March 27 2014).

 

Hopefully this will help avoid some of the basic errors that can be made when implementing Section Access.

 

Colin Albert.

Labels (1)
Comments
Not applicable

Thanks  I've resolved the problem.

Not applicable

I want to implement NTNAME based section access but only for few users and I want other users to see all the data even if they are not included in the section access

For ex : I have one AD group (e.g. myteamadgroup) where 10 team mates are member of this group. In my data model there is one REGION field which has data like REGION1,REGION2,REGION3,REGION4

I want to design section access only for 4 members with restriction on REGION field (e.g. when they log in to dashboard then they should see only REGION1's data) and rest of members should login to the dashboard and should see all the data (Even if they are not part of section access) Is this possible?

Colin-Albert

If Section Access is enabled in a document then it will apply to all users.

The best security is to use NTNAME access as this is more difficult for users to bypass.

You could use NT name for the 4 users and the others use a QlikView login and password. If the NTNAME is not recognised in section access, then the users will be prompted to enter a QlikView username to access the document.

You can restrict the 4 named users to just view the REGION1 data, but you will need to include REGION2, 3 & 4 in the section access table as DUMMY entries if not already listed. This is because * in section access, means "all values listed in the section access table", not "all values in the data column".

Colin-Albert

Version 6 now includes a link to the list of Section Access documents collated by Marcus_Sommer

Section Access

ahmar811
Creator III
Creator III

Thank you for sharing your knowledge

robert_mika
Master III
Master III

Than you Colin.

Great resource.

Anonymous
Not applicable

I am starting in the secutity QV , I really apreciate this information

Not applicable

thank you for sharing. really appreciated.

your example 4, "adds extra DUMMY rows to the section access table so the * entries can now access all cost centres." If there are many possible values for cost centres, how to handle it? Thank you.

Anonymous
Not applicable

I have the same issue where I want Users to see ALL DATA on ALL SHEETS, except for 1 sheet I want to limit the access based on a field.  How do I do this so that I do not restrict data throughout ALL OF THE SHEETS, but only on 1 SHEET?

Anonymous
Not applicable

Hi Andrew,

Did you ever get your issue resolved?  I can't seem to figure out a way how to do the same thing you were trying to do.  Thanks in advance.

Version history
Last update:
‎2022-10-07 09:22 AM
Updated by: