In Oracle Financial Crime and Compliance Management Cloud Service, users have roles through which they gain access to functions and data. Users can have any number of roles.
The following figure shows the User Persona Details:
NOTE:
User-Group mapping changes from IDCS will take 5 minutes to sync with application. If these changes are made during active user session then it will be reflected on next login.
Role-based security in Oracle Financial Services Crime and Compliance Management Cloud Service controls who can do what on which data.
This table summarizes role-based access.
Component |
Description |
Who |
Is a role assigned to a user? |
What |
Is a function that users with the role can perform? |
Which Data |
Is the set of data that users with the role can access when performing the function? |
This table provides some examples of role-based access.
Who |
What |
Which Data |
Data Administrator |
Can perform Data Preparation and ingestion |
Business Data |
Case Analyst |
Can view cases and update cases |
Business and Operational Data |
The following table provides the User Group, User Role mapping, and activities.
Group |
User Role |
Functionality |
Identity Administrator |
Identity Administrator |
· View the reports · View the object storage · View the OAUTH credentials · Perform the Identity and access management operations |
Identity Authorizer |
Identity Authorizer |
Authorize the Identity and access management operations |
IDCS Administrator |
IDCS Administrator |
· Create users · Map users to IDNTY_ADMIN group · Map users to IDNTY_AUTH group |
Compliance Agent User Groups |
||
Administrator Group |
Administrator |
· Add a new user · Remove the existing user · Configure Transaction Monitoring System · Create segments · Run an experiment · Compare two experiment · Add and remove offerings · Add and remove control sets |
User Group |
User |
· Configure Transaction Monitoring System · Create segments · Run an experiment · Compare two experiment · Add and remove offerings · Add and remove control sets |