This Bulletin updates the list of PaySR security classes available to agencies and describes the process for assigning each agency PaySR user to the appropriate security class. This bulletin is being sent to all Payroll Officers, Agency Liaisons and Coaches for Conversion Group 2.

Security Process

Agencies in Conversion Group 2 must complete a copy of Attachment A to assign a security class for each PaySR user and return these forms to PaySR by August 10. (This date is a change from the checklist recently sent to Liaisons). Agencies in Conversion Group 3 will be asked to provide this information at a later date.

Once users are provided access to PaySR they will no longer have access to the current payroll system. The current Payroll History file will be available online through PaySR. Agency users with access to security classes 1 and/or 2 will have access to outside history from the legacy system. For additional details regarding access to payroll history see Bulletin No. 26.

OSC has provided Security Officers in Group 1 agencies a revised technical Security Bulletin with PaySR-specific information. This Bulletin will be sent to Group 2 agencies shortly along with a revised form that will also be provided to Group 1 agencies. Please use the form provided with that bulletin to make any necessary modifications to security assignments.

Attachment B is a table of security base classes available to agencies. The functions and panels available to each base class are noted. (Agencies managing positions that are not under the jurisdiction of the Department of Civil Service will have additional position management security access options not listed in this Bulletin.)

Attachment C lists security classes which represent various combinations of the base security classes 1-8.

Base classes 1 - 6 represent the functional groupings relevant to all agencies. Base class 7, Job Requests, was developed to provide agencies the ability to give personnel staff access to the job request panels. It includes panels found in base classes 1 and 2, therefore a user with access to both of those classes will not need class 7. Agency personnel staff can begin the promotion transaction in PaySR by entering the new position number (see Job Request panel, Attachment D) and saving the panel without yet submitting the transaction to OSC. Agency payroll staff may then complete the transaction by entering the new salary, re-saving and submitting the request to OSC.

Base class 8, Workers Compensation/Concurrent Hire was developed to allow access to the panels necessary for Workers’ Compensation leave, but not other personal data. It includes panels found in base class 1. Therefore, a user with access to class 1 will not need class 8. Agencies that frequently add employees in concurrent hires may also use base classes 7 and 8 together (see security class code 478U in Attachment C) to allow for the concurrent hire without access to personal and tax or deduction information.

The Super User class provides the ability to view and add or update all employee information. The Super Viewer class provides the ability to look-up or view any employee information, but not to add or update.

Security for Query

Users’ access to the query database can either mirror their access on the production database, meaning that they will be able to query only those tables tied to the panels for which they have access, or there is the option to "View All" for Query security.

Action Steps

• By August 10, 1998, Agency Liaisons in Conversion Group 2 should complete a security form (Attachment A) for each agency employee with access to PaySR. The information required on this form includes:

User Identification - Name, phone, agency name and agency code

A. Security Class - Based on the table provided with this Bulletin (Attachment C), please indicate the security class code to which this user should be assigned. (Please note that only one code may be selected. Many classes represent a combination of security groups.) Indicate the specific agency codes, or range of agency codes, to which this user should have access for PaySR Production.

B. Query Access - Indicate if this user should have access to the query database panels to only run existing queries, or be able to create queries. (Completion of the PeopleSoft Query for PaySR training is a prerequisite.) Indicate if you wish the user’s security class to be the same for Query as for the production database, or access to view all. Indicate the agency codes the user will have access to for query.

C. Report Access - Indicate if this user should have access to PaySR-produced reports, such as the payroll register. Indicate the agency codes the user will have access to for viewing PaySR-produced reports. PaySR uses Reveal C/S software for viewing PaySR-produced reports. See Bulletin No. 21 for more information on PaySR Reports.

D. Signature - The Agency Security Coordinator must sign each form.

Mail these forms to: Theresa Flynn, PaySR Project, 194 Washington Avenue, Albany, NY 12210.

• Prior to conversion, PaySR will provide Conversion Group 2 agencies with user IDs and passwords.

Questions on this Bulletin?

• Payroll Officers should contact their Agency Liaison.
• Agency Liaisons should contact Audrey Seidman at (518) 473-7388 or aseidman@osc.state.ny.us.

A. PaySR Security: User Configuration
B. Security Base Class Descriptions
C. PaySR Security Class Codes
D. Job Requests Panel