|
|
 |
 |
|
The Pathways Database Publisher comes with a complete built-in Security System. This system
allows publishers to define the users that will be allowed access to the system, as well as the
types of access they will be given. If a publisher chooses, the security feature may be turned off.
With security turned off, access to the system will be granted to all users without restriction.
|
|
|
|
|
To take advantage of the security features built into the Pathways system, publishers must define a
User ID and Password for all personnel who will be allowed access to the system. Once user
IDs have been defined, the next step is to define the types of access each user will be granted. Publishers
can restrict users to specific publications as well as to specific functions related to those publications.
|
|
|
|
|
|
|
|
 |
|
|
|
Using the security modules, it is possible to allow a systems manager unlimited access to all publications,
while restricting a data entry clerk to limited access for a single publication or a group of publications.
It is also possible to give data entry clerks access to some areas of the system while restricting access
to others. As an example, they can be given access to maintain editorial information and denied access
for maintaining desktop publishing interface templates. Publishers may also restrict access to “read
only” for some users. By doing so, the publisher has eliminated the possibility of the user inadvertently
altering database information.
|
|
|
|
|
A Copy Button makes it extremely easy to establish new users that have a similar security to a
user already established in the system. It also allows a particular user's security clearance information
to be duplicated from one publication to another.
|
|
|
|
