User Groups

The following table gives details about the User Groups in the Oracle Financial Services Model Management and Governance application.

Table 3-1 User Groups

User Group Name	User Group Description
IDNTYADMN	Identity Administrator group
IDNTYAUTH	Identity Authorizer group
MDLREV	The Modeling Reviewer Group. Users mapped to this group have access to the menu items in the OFS MMG application that are related to model review activities.
MDLAPPR	The Modeling Approver Group. Users mapped to this group have the rights to approve models created by the users.
MDLBATCHUSR	The Modeling Batch User. Scheduler can use this Group for executing batches.
WKSPADMIN	The Workspace Administrator Group. Users mapped to this group have access to create and populate workspaces. For vieweing the MMG landing page this group is required.
MDLUSR	The Modeling User Group. Users mapped to this group have access to all the menu items in the OFS MMG application that is related to model creation.
DSUSRGRP	Data Studio User Group This User Group provide access to modify Interpreter configurations.
DSREDACTGRP	Roles for applying redaction in graph. This group will be applicable to only those users for whom graph redaction is required.
OBJMIGADMIN	Users mapped to this group have access to Object Migration links and UI to perform import or export of objects.
GRPADMIN	The Graph Administrator Group. Users mapped to this group have access to all the menu items in the OFS MMG Application related to graph and Pipeline/Refresh graphs related health services.
GRPUSR	The Graph User Group. Users mapped to this group have access to all the menu items in the OFS MMG Application related to graph and Pipeline/Refresh graphs related health services.
SCHEDULERADMIN	This group contains all the roles and functions related to the Scheduler feature. The SCHEDULERADMINACCESS role contains has all the functions that are related to LINKSCHDLR. The new function LINKSCHDLRCNF, enables you to open the scheduler configuration.

If you create a custom user group (other than the seeded OFS MMG groups) and want users in that group to access the OFS MMG Studio operations, then you must add the group in the following configuration files:

mmgstudio/conf/application.yml

mmgstudio/conf/ofsaa-permissions.init.yml

These updates ensure that the custom group is recognized by OFS MMG Studio and is mapped to the required Studio permissions.

Note:

Enter group names in UPPERCASE, because AAI/OFSAA groups are stored and validated in uppercase.

Note:

At the first-time login, User Group mappings are initialized from AAI/IDCS for the newly provisioned users. These will be reflected in MMG Admin Console in next MMG login.

If User Group mappings are deleted in AAI/IDCS, it would not delete in MMG Admin Console. Admin needs to delete this in MMG Identity screens too.

Only the group with MDLSUMM role will be displayed in the Workspace provisioning steps.

MDLSUMM function is mapped to the MDLACCESS role.