To
control the primary level of data access of users of the system.
|
||
Subsystem
|
||
Structure
|
Two
Blocks |
Person |
|
Navigation
Buttons invoke: |
Organisational
Unit Restrictions form Correspondence
Type Security form |
|
Person
|
Explanation
|
The
Person block displays personal details that have already been recorded
in the System, for a person. Additional information may be added in
this block to record the person as a System user.
The navigation buttons invoke restriction forms that allow the user's
access to be restricted to data for particular organisational units
or data for particular correspondence types. |
To
record a person as a System user using the Maintain System Users form:
|
|
|
Rules:
|
Person Role Grant
|
Explanation
|
Having
established a person as a System user, it is necessary to grant them
access to the areas of the System that they are entitled to use. This
is accomplished by assigning security roles to them. Security roles
define the primary levels of access to the System and are created and
maintained by the Database Administrator. Access
can be further controlled by the use of the Auto Enable checkbox. If
the checkbox is deselected for a role grant, the user is only
able to access data applicable to that role by using Callista forms,
jobs and reports. If the checkbox is selected for the role grant,
the user has the same data access via Callista but is also able to access
that data using applications other than Callista (eg. third party reporting
tools). |
Example
|
|
To
grant a security role to a System user using the Maintain System Users
form: |
|
|
|
To
remove a security role from a user using the Maintain System Users form:
|
|
|
|
To
inquire on the security roles granted to an individual user using the
Maintain System Users form: |
|
|
Rules:
|
Last
modified on 11 March 2002