Specifications

System Security 121
ID Works Basic Version 5 Administrator’s Guide
User Privileges
As a System Administrator, you determine what actions a user can
perform when you add a new user. You can also change an existing
user’s privileges. In either case, a wizard enforces dependencies
among privileges.
You can base privileges on an existing user. For example, you can
create a generic Production operator user, ProdOp, that has the
privileges you want all your Production operators to have. Then,
when you need to authorize a new Production operator, you can copy
privileges from the ProdOp user, adding and deleting privileges as
necessary for the new Production operator.
You can restrict users to certain projects. For example, a school
might hire temporary workers to help with enrollment at the start of
the term. If you restrict those workers to the ID Works project for
enrolling students, they will not be able to access other ID Works
projects, such as the one for making faculty IDs.
There can be more than one user with System Administrator
privileges, and there must be at least one user with System
Administrator privileges at all times. To ensure that you do not delete
the last System Administrator, you cannot delete your own user
account.
Requiring Login after Inactivity
Because the Production application is used to modify a database and
print cards, you may want to require that the user log in again after a
period of inactivity. This would help prevent unauthorized users from
printing cards or starting another ID Works application when a
Production operator forgets to log out before leaving the workstation
unattended.
You can set the length of the inactivity period from 5 to 30 minutes in
5-minute increments. See the Administrator online help topic,
“Configure Automatic Production Log Off” for step-by-step
instructions.
When the specified amount of time has elapsed without Production
application activity, a dialog box similar to the following appears.