Three levels of passwords are available in GainSeeker. The first password is a login password that may be assigned to the user. The other two passwords are assigned to a configuration.
The user's login password controls access to any GainSeeker module. It is assigned when you set up a user. This password confirms that you are an authorized user of the system, and permits you to use a configuration (with associated table names, file paths and field labels) and a role. If your role does not permit access to a GainSeeker module, you will not be able run that module – even with the user's login password.
In addition to the user's login password, each configuration may have two passwords associated with it. These passwords (level one and level two) are another layer of protection to make sure that only authorized people can use each part of the program.
Used in combination with users, roles and configurations, these three passwords provide maximum flexibility and control in your system.
For example, you can grant a data entry operator and a quality technician rights to use the Data Entry module. Both people will have a user login name and password that grant them access to that module. While in that module, the quality technician may need to modify the standards—for example, changing the sample size or the historical control limits. Thanks to the role assignments, you can ensure that the technician can get to that function, but the operator cannot.
But what happens if the technician walks away from the computer without logging out, and the operator starts to enter data without logging in? In this situation, the operator is now logged in as the technician and can use the same functions of the program granted to the technician. Fortunately, there is one important difference: the operator does not know the level one and level two passwords from the configuration and therefore cannot access those parts of the program that are protected by these passwords.