4.2.13.2 Access Enforcement
This topic provides information on access enforcement.
Access management in Oracle FLEXCUBE can be done in four steps.
- Module level -
In such a case the user cannot view even the menu list of the FCIS when he tries to login into the restricted module. Thus, no transactions could be performed.
- Roles wise - As described above basing on the user-roles mapping, the user can access different modules in FCIS. For an example, a bank clerk will have access to customer creation, account opening, term-deposits opening and liquidation screens, but he will not have access to SMDUSRDF, which is for user creation.
- Function-ID wise - Here, the user can be restricted to launch even the UI on clicking on the menu list.
- Product/ Account class wise - Here, the user can be prevented access to certain account classes or products. This will disable him from creating any accounts or transactions using those prevented account class and product respectively.
Parent topic: User Management