21.01.2013 Views

QlikView Reference Manual.pdf - QlikCommunity - QlikView

QlikView Reference Manual.pdf - QlikCommunity - QlikView

QlikView Reference Manual.pdf - QlikCommunity - QlikView

SHOW MORE
SHOW LESS

Create successful ePaper yourself

Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.

If an access section is defined in the script, the part of the script loading the ”normal” data must be put in a<br />

different section, initiated by the statement section application.<br />

Example:<br />

Section Access;<br />

Load * inline<br />

[ACCESS,USERID,PASSWORD<br />

ADMIN, A,X<br />

USER,U,Y ];<br />

Section Application;<br />

Load... ... from... ...<br />

29.5 Access Levels in Section Access<br />

Access to <strong>QlikView</strong> documents can be authorized for specified users or groups of users. In the security table,<br />

users can be assigned to the access levels ADMIN or USER. If no access level is assigned, the user cannot<br />

open the <strong>QlikView</strong> document.<br />

A person with ADMIN access can change everything in the document. Using the Security page in the Document<br />

Properties and Sheet Properties dialogs, a person with ADMIN access can limit the users’ possibilities<br />

of modifying the document. A person with USER privileges cannot access the Security pages.<br />

Note!<br />

ADMIN rights are only relevant for local documents! Documents opened on a Server are always accessed<br />

with USER rights.<br />

29.6 Section Access System Fields<br />

The access levels are assigned to users in one or several tables loaded within the section access. These tables<br />

can contain several different user-specific system fields, typically USERID and PASSWORD, and the field<br />

defining the access level, ACCESS. All Section Access system fields will be used for authentication or<br />

authorization. The full set of section access system fields are described below.<br />

None, all, or any combination of the security fields may be loaded in the access section. It is thus not necessary<br />

to use USERID – an authorization can be made using other fields, e.g. serial number only.<br />

ACCESS A field that defines what access the corresponding user should have.<br />

USERID A field that should contain an accepted user ID. <strong>QlikView</strong> will prompt for a User ID and<br />

compare it to the value in this field. This user ID is not the same as the Windows user<br />

ID.<br />

PASSWORD A field that should contain an accepted password. <strong>QlikView</strong> will prompt for a Password<br />

and compare it to the value in this field. This password is not the same as the Windows<br />

password.<br />

SERIAL A field that should contain a number corresponding to the <strong>QlikView</strong> serial number.<br />

Example: 4900 2394 7113 7304<br />

<strong>QlikView</strong> will check the serial number of the user and compare it to the value in this<br />

field.<br />

402

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!