Overview of Security Configuration
During implementation, you evaluate the predefined roles and decide whether changes are needed. If the predefined security reference implementation doesn't fully represent your enterprise, you can change it.
For example, the predefined Admissions Coordinator
job role includes View Student Management
Rules privileges. If some of your admissions coordinators don't handle
rules, you can create a admissions coordinator role without this privilege.
To create a role, you can either copy an existing role and edit it,
or create a new one.
All predefined roles have many function security privileges and data security policies. They also inherit duty roles.
You can identify predefined application roles easily
by their role codes, which all have the prefix ORA_. For example, the role code of the Admissions
Coordinator
application job role is ORA_HEQ_ADMISSIONS_COORDINATOR_JOB.
If you need only minor changes to a predefined job or abstract role, copy the role and edit the copy to add or remove duty roles, function security privileges, and data security policies, as appropriate.
Consider creating a role if it has very few privileges and you can identify them easily.