2 Enable Auto Authorization
This topic explains why authorization is required and how to enable auto authorization and its features.
Normal Process of Authorization
Most of the information that you enter in to the system needs to be authorized to be effective. Except for the static information that you typically enter in to the system only once, all other information must be authorized. Authorization is required for all maintenance as well as transactional information in the system.
When you enter information related to any of these events into the system, the record that is initially saved when you complete the data entry is retained in the system as unauthorized information, which must be subsequently authorized to become effective.
Usually, authorizing information in the system is an activity that follows a maker-checker concept, i.e., the user that enters the information must be necessarily different from the user that authorizes the information. Therefore, whereas one user group will have access to functions that involve entering information into the system, a different user group has access to the functions that involve information authorization, and there is no overlap of access privileges.
Auto-authorization
In some environments, the user that enters the information needs to be able to authorize it simultaneously. In such cases, the maker-checker concept leads to unnecessary delegation of activity, which is undesirable. This means that in such an environment, the user that enters the information must, on saving the entered record, be able to authorize the record.
For such environments, the auto-authorization function is provided by the FCIS system. When this function is used, the save operation in any screen that involves data entry (apart from static information screens) will also invoke and perform the authorization for the records that have been entered.
It is possible to be selective about the business functions for which you need to use the auto-authorization feature. This means that you can enable the auto-authorization feature for the functions for which you require simultaneous authorization on saving the record, and you can keep it disabled for others, allowing them to go through the normal maker-checker process of authorization.
Table 2-1 Features and Auto-authorization Facility
Features | Auto-authorization Facility |
---|---|
Enable Auto-authorization Features for Business Users |
The Administrator users can map the business users to the menu items, and make auto-authorization feature allowable for any business user menu item mapping. All business checks, validations and processes that must be performed when the authorization happens will be triggered immediately following the use of the save operation, when the auto-authorization feature is allowed. |
Enable Auto-authorization Features for a User Group |
The Administrator users can enable (or disable) auto authorization rights at a user group level. Any user roles and / or users associated with the user group would inherit the auto authorization privileges assigned to the user group. If a user ID is associated with multiple user roles, the most restrictive privilege assigned to the roles will be applicable. |
Enable Auto-authorization Features for Data Operations |
You can enable (or disable) the auto authorization feature for data operations in the New mode or the Amend mode, including data entry either for reference information, investor accounts or transactions. For transaction entry operations in either mode, you can enable (or disable) auto authorization for transactions involving any of the following circumstances:
|
This topic contains the following sub-topics:
- Using Auto-Authorization Feature
This topic gives information on using Auto-Authorization Feature. - Process Auto Auth
This topic provides the systematic instructions to map user groups to the tasks for which auto-authorization is applicable. - Enable or Disable Auto-authorization for a User Group
This topic provides instructions to enable or disable Auto-authorization feature for a User Group. - Set up Auto Auth screen based on Fund and RPO code
This topic gives instructions to set up Auto Auth screen based on Fund and RPO code. - Operations on Auto Authorization Records
This topic provides the systematic instructions to perform the basic operations on the selected records.