C.2 Managing User Groups

The following sections describe how to manage User Groups.

Defining User Group Maintenance Details

For more information on defining user group maintenance details, see Identity Management in the Oracle Financial Services Analytical Applications Infrastructure User Guide .

Adding New User Group Details

For more information on adding new user group details, see Identity Management in the Oracle Financial Services Analytical Applications Infrastructure User Guide .

Mapping Users to User Groups

When mapping users to user groups, consider the following:
  • One user can also be used against multiple roles. If multiple roles are allocated to a single user, then the availability of actions depends on the Four Eyes approval option. If Four Eyes approval is off, then the user can take all actions available by the allocated roles, with no duplicates. If Four Eyes approval is on, then action linked to a role that does not require Four Eyes approval takes precedence if there is a conflict.
  • Users will have read-only access to Alert if they have been mapped to the ALERTVIEWERGRP user group. Other user groups such as Supervisor, Analyst, Auditor, Executive groups will not be given access to Alert Viewer.

For more information on mapping users to user group, see Identity Management in the Oracle Financial Services Analytical Applications Infrastructure User Guide .

Mapping a User to a Single User Group

If a user has only one role then that user can be mapped to a single User Group associated with that User Role. For more information on mapping a user to a single user group, see Identity Management in the Oracle Financial Services Analytical Applications Infrastructure User Guide .

Mapping a User to Multiple User Groups

If a user has more than one role within FCCM (that is, within both Alert Viewer and Enterprise Case Management), then the user must be mapped to the different User Groups associated with the corresponding role. When the user logs into FCCM, the user access permissions are the union of access and permissions across all roles.

Mapping a Function to a Role

Functions must be mapped to appropriate Alert and Case User Roles through Function-Role Map function, which is available in the Security Management System, by logging in as the System Administrator in the OFSAAI toolkit. All Alert Viewer user roles should be mapped to the function AMACCESS in order to access an alert. Users of roles that are not mapped to this function cannot access the details of the Alerts.