APPX security assists in protecting sensitive information that is stored on your system. You can deny access to any field in an APPX-based system. There are multiple ways of protecting fields; you can protect them at the domain (field template) level, at the file level, or by individual field or work field. Additionally, you can prevent a user from executing any process. You can prevent a user from adding, deleting, or changing records in a file. Also, you can define a Record Access Security field that prevents a user from even knowing that a particular data record exists.
You accomplish this by assigning a security code to a domain, file, field, or work field, or to a process or set of processes, or to a set of records in a particular file. A security code is a four-digit number from 0000 to 9999. Rights to these codes are established in Security Profiles, and each user on your system can be assigned to a Security Profile. Security profiles can cover all databases or be assigned to a particular database.
There are many ways to set up Security Profiles as a means of managing field, record, and process protection on your system. For example, Security Profiles can be set up for “Management” and “Clerical”, or for “Accounts Payable” and “Accounts Receivable”, or even for “Security Management” if you wish. If needed, you can set up a separate Security Profile for a given user, although most users can be placed into general categories. You should spend some time planning your security system before setting up and assigning Security Profiles. You will want security to be easily maintained.
In order to secure your system effectively, several steps are necessary:
· Set up Security Profiles that define the security codes that will protect various areas of your system.
· Assign each user to an appropriate Security Profile.
· Enter security codes for the domains, files, fields and work fields you want to protect according to the hierarchy established by your Security Profiles.
· Enter security codes to protect processes or sets of processes, both for execution and for capability to add, delete, or change records in files.
· For files that contain individual records you want to secure, establish Record Access Security fields and design input processes that allow you to maintain a security code for each record you want to protect.
The remainder of this chapter describes how to set up Security Profiles and how to define what each user will be allowed to see or maintain within your system. Another chapter in this manual, Application Security Management, describes how to enter security codes to protect domains, files, fields, work fields, and processes. In addition, the Designer Reference Manual contains information regarding the establishment of Record Access Security. Thus, the implementation of security is a joint responsibility of the system administrator and the application designer.