A security record must be established on the Security update [U0706] before a user can access LeasePak. Each person is given or denied access to each update and report. It is possible to create a security record for one user and then copy it as the model for other users.
If access is denied, that update or report does not appear on the user’s menu at all. Thus it’s unlikely that a user will see all possible updates and reports covered in the Reference Guide. An update may not appear on your menu because your security record does not allow access to it, or because it is part of an optional LeasePak module which your company has not installed.
Passwords may be changed in a 2-step process. The user selects a new "client" password, then informs the system administrator. The administrator must change the client, Sybase and UNIX passwords.
LeasePak security is assigned by individual user, essentially allowing as many security levels as there are users. Security settings for one users may be cloned for others to reduce data entry and allow standardized security for groups. Each update, report, and special function that the user may (or may not) access is designated through LeasePak’s Security update [U0706]. Any update, report, or special function that is not available to a given user does not appear on that user’s menus and may not be selected by that user.
The list of reports and updates that a user may access can be changed at any time, but only by someone with security access to LeasePak’s Security update [U0706].
There are several security measures at the system level. The first is the sign on procedure. All users are assigned a user name and a password. Both must be verified by the system before access to LeasePak is allowed. The password does not appear on the screen when it is being typed in, preventing unauthorized access to a user’s password. LeasePak provides a special function that allows a user to change his/her password, which should be done regularly. The user name also is used as a signature for all General Ledger transactions performed.
After a user signs on, LeasePak software guides the user through updates or reports, using menu screens. Access to the operating system is allowed for only special, system manager-type accounts.
All users of LeasePak have a group number, set by the system manager. Only members of this group may access the LeasePak database, preventing access by other (non-leasing) users of the system.
LeasePak also implements a data recovery system. That is, if any unexpected event should occur (power failure, etc.) that causes an abnormal exit from LeasePak, all incomplete updates are automatically reversed to their original values when the user logs back onto the system or when another user recovers the incomplete process. No other user may access the unrecovered data until recovery has been performed. This insures integrity of the database.
©
2001 by McCue Systems Incorporated.
All rights reserved.
The information contained in this document is the property of McCue Systems, Inc. Use of the information contained herein is restricted. Conditions of use are subject to change without notice. McCue Systems, Inc. assumes no liability for any inaccuracy that may appear in this document; the contents of this document do not constitute a promise or warranty. The software described in this document is furnished under license and may be used or copied only in accordance with the terms of said license. Unauthorized use, alteration, or reproduction of this document without the written consent of McCue Systems, Inc. is prohibited.
