This page (revision-5) was last changed on 26-Nov-2021 10:22 by JMyers

This page was created on 26-Nov-2021 10:22 by KHanson

Only authorized users are allowed to rename pages.

Only authorized users are allowed to delete pages.

Page revision history

Version Date Modified Size Author Changes ... Change note
5 26-Nov-2021 10:22 2 KB JMyers to previous
4 26-Nov-2021 10:22 2 KB JEscott to previous | to last
3 26-Nov-2021 10:22 2 KB RForbes to previous | to last
2 26-Nov-2021 10:22 2 KB KHanson to previous | to last
1 26-Nov-2021 10:22 572 bytes KHanson to last

Page References

Incoming links Outgoing links
IDAA
IDAA

Version management

Difference between version and

At line 4 changed one line
text on form
Authorization Areas divide an organization into areas in order to have employees’ information secured from unauthorized user access.
At line 6 changed 3 lines
;[FieldNameInHdr]:description
%%warning This function is for viewing purposes only; you may not edit the data.%%
%%information This function is [date sensitive] and changes made in these areas below the [date navigator] may be split with a new effective date.%%
This section explains the Define Authorization Areas (IDAA) screen and its associated fields.
At line 10 changed 3 lines
----
[{Image src='ILDI_Tabname.JPG' width='360' align='right' link='attach/ILDI/ILDI_Tabname.JPG'}]
!!Tab Headings
Authorization areas are an abstraction which usually follows department lines, but may span multiple departments or even split departments. They are used for controlling access to employee records by these areas.
At line 14 changed 2 lines
!Section Headings within in each tab
;[FieldName]:Definition
The areas are defined by entity. To set up authorized access by a user, an authorization area is placed on the security rights record for that user (found on the Maintain Security Rights (IMSV)form).
As an alternate method to defining individual records for each authorization area, ePersonality allows you to assign the authorization areas using a pattern match. For example, if you have several Authorization Areas that begin with ‘Sheriff’ (Sheriff Jail, Sheriff Clerical, Sheriff Accounting), you may want to assign all those areas to a specific person. You may give that person authorization by indicating AUTH AREA MATCH "SHERRIF%".
The authorization area is assigned at the department level, which will default down to the position code and, in turn, default down to an employee's assignment when they are assigned that position or department.
Employees are assigned to authorization areas and only a user with the appropriate the system will be organized into authorization areas, which are maintained on the employee’s assignment record. If the user's allowed authorization area matches the employee’s authorization area, then that user can access the employee’s information.
‘Authorization Areas’ are established for the ‘operational’ entities not the ‘legal’ entities. Authorization area codes may be changed at any time and the effect of the changes will be seen immediately throughout the system.
‘Define Authorization Areas’ Usage and Examples
Authorization Area data is stored in the [P2K_CM_AUTHORIZATION_AREAS] table.
;[Entity | ENTITY_CODE]:This field is the entity to which the authorization area belongs.
;[Auth Area | AUTHORIZATION_CODE]:The authorization code is a user-defined code that uniquely identifies the authorized area within the organization.
;[Description | DESCRIPTION]:This field describes the authorized area controlled by the authorization code.
This page (revision-5) was last changed on 26-Nov-2021 10:22 by JMyersTop