VISTA Plus for MPE Administrator's Guide

Security
7-5
Report Security
All users can read a report until one or more security masks are assigned to it. Once a security mask
is assigned, then only the users matching the security mask are allowed to read or delete a report. A
user is not allowed to delete a report unless that capability has been assigned to the user or the user
is also the report creator. Read and Delete security is assigned to a report in the Report
Maintenance window described in Chapter 5 of this guide.
• When you create a report, you are automatically given read, print, and delete access to that
report. A creator is defined as the session, user, and account that created the report.
• Users with System Manager capability are allowed to read, print, and delete reports in the
system regardless of report security settings. This feature can be disabled by setting the
VISTAINI file’s $ALLOW-SM-SYS-CAPABILITIES option to OFF.
• Users with Account Manager capability are allowed to read, print, and delete reports created in
their account regardless of security settings. This feature can be disabled by setting the
VISTAINI file’s $ALLOW-AM-SYS-CAPABILITIES option to OFF.
Security Masks
Security masks (@,MANAGER.PAYROLL) defined in the Report Maintenance window consist of
a session or job name, user name, and account name. They are linked to a report record and utilized
when assigning read and delete access to a user. Security masks provide the capability to reference
a specific user or a group of users. When assigning security to a report, wild cards for session, user
and account names can be specified within a security mask to reduce the transactions required to
define multiple users that can read and delete a report. When the security mask
@,MGR.PAYROLL (with read security) is assigned to a report, all users logged into the system as
MGR.PAYROLL will be allowed to read the report. Shown below are sample Security Masks:
************* Report Security ********************
Session,User.Account Read Delete Print
[supvisor,mgr.payroll ] [Y] [Y] [Y]
[clerk,jessie.payroll ] [Y] [N] [Y]
[@,user.mfg ] [Y] [N] [Y]
Since wild cards are supported for Session and User.Account, you must list specific users before
users that qualify based on a wild card definition. This prevents a user from matching a wild card
definition before an entry is located for the user.
Note. Report security is independent of report viewing and can be defined before
reports are captured and stored into folders.