Top of SEC | Index | Table of Contents | Feedback |
SECF0032 - Maintain Organisational Unit User Restrictions
Purpose |
To record the Organisational Units for which a user may access related data. |
|
SubSystem |
Security |
|
Normally Run By | Administration specialist | |
Anticipated Frequency | As required | |
Structure | Blocks | Person |
Organisational Unit Restriction |
The Person block contains:
The Organisational Unit Restriction block contains:
|
Rules/Notes: |
Person block explanation This form is accessed from the Maintain System Users form (SECF0021). It is used to limit an individual user's data access to data related to specific organisational units. The Person block displays previously recorded user details. Query functions cannot be performed in this block. Refer to Security Restrictions and Access to Data for important information. Organisational Unit Restriction block explanation The ability of a user to access data is initially determined by the security role(s) granted to the user. That access can then be further refined by the use of security restrictions. Organisational unit restrictions reduce the set of data to which a user has access in the following ways:
Users granted access to an organisational unit which is the parent of other organisational units automatically have access to the child (and grandchild etc.) organisational units. If a child organisational unit is also specified as a restriction, this restriction overrides the parent organisational unit inheritance. For example, if restricted select access for a faculty is recorded for a user, the user also inherits restricted select access for any schools recorded as children of the faculty. If one of the schools is also recorded, but with update, insert and delete access specified, the user has restricted select access to the faculty and all schools recorded as children of the faculty, but can update, insert and delete records for that school. Some institutions are structured such that user data access might be restricted to specific groups of organisational units. To facilitate this, a group of organisational units can be placed under a dummy parent organisational unit by:
The dummy organisational unit can then be granted to users as an organisational unit restriction, with users automatically inheriting data access for the group members. Additional information about the operation of user restrictions, and in particular 'certification' of functions for their use, is contained in Security Restrictions and Access to Data. |
Rules/Notes:
A
user may be granted a role that provides unlimited access to organisational
unit related data. If they have no entries under organisational unit
restriction, they will still have unlimited access to organisational
unit related data. |
To create an organisational unit restriction for a user using the Maintain Organisational Unit User Restrictions form:
|
Rules/Notes: Restrictions only apply to users with a security role which has the appropriate restriction object registered against it. Selecting an Update, Insert or Delete checkbox enables a user to perform that function for the organisational unit. Deselecting a checkbox will stop a user from being able to perform the function. Selecting a Restricted Select checkbox for any organisational unit restriction record causes the Restricted Select checkboxes for all records to be selected. Inquiry access is then restricted to the organisational units recorded here. Adding restrictions to a user reduces the access inherited from their security role(s). Access cannot be increased beyond that specified by their security role(s). For example, if the role prevents deletion, setting the delete indicator in this form will not allow the user to delete. A record cannot have all three of Update, Insert, Delete, checkboxes set without having Restricted Select set, as this constitutes no restriction of access. |
To remove an organisational unit restriction from a user using the Maintain Organisational Unit User Restrictions form:
|
|
To modify an organisational unit restriction for a user using the Maintain Organisational Unit User Restrictions form:
|
Rules/Notes: The Organisational Unit field is protected against update. To change an incorrect organisational unit, the incorrect organisational unit must be deleted and a new record inserted. |
Last Modified on 12 December, 2003