How do you create a new custom recruiter role that restricts access to candidate offers?

Access to functionalities like candidate offers is controlled by function security privileges within a job role. The best practice is to use the Security Console to copy a standard role (e.g., Recruiter), rename it, and then remove the specific privileges related to offer management (e.g., Manage Job Offer, View Job Offer). This new custom role can then be assigned to users, ensuring they have all other necessary recruiter permissions but are explicitly restricted from accessing the offer functionality.

B) Transaction Design Studio is used to modify the user interface (e.g., hide fields or change labels), not to enforce functional security or remove access to core actions.
C) User types in Recruiting are used to configure different process flows (e.g., for executive vs. professional hiring), not to control security privileges.
D) Relying on a person's job title to restrict access is not a security mechanism. Access must be configured explicitly through security roles and privileges.

- Oracle Fusion Cloud HCM, 24B, "Securing HCM", Chapter: Security Implementation Tasks, Section: Copying Job Roles. (Doc ID: F83059)

- Oracle Fusion Cloud HCM, 24B, "Securing HCM", Chapter: Role-Based Access Control, Section: Function Security Privileges. (Doc ID: F83059)