Thank you for supporting the Cloud Customer Connect Community in 2024. It's a gift to work with you!

Look back
You're almost there! Please answer a few more questions for access to the Applications content. Complete registration
Interested in joining? Complete your registration by providing Areas of Interest here. Register
Get Started with Redwood for Oracle Cloud HCM   Begin Now
To ensure that questions get required attention from community members and are NOT left unanswered, it’s important for the author to indicate (by selecting “Yes” or “No” when prompted) whether the question was answered. (newly added) Please note that it is also important to respond to EACH comment your question receives. Your Yes or No response ensures an accurate status for your question.

For more information, please refer to this announcement explaining best practices for getting answers to questions.

Restrict recruiter from creating requisition based on Primary Location

edited Jan 12, 2024 1:51PM in Recruiting, Opportunity Marketplace 1 comment

Summary:

Restrict recruiter from creating requisition based on Primary Location.


Content (please ensure you mask any confidential information):

I implemented recruiter security based on Oracle Note "Oracle Fusion Recruiting Cloud: Recruiter Access to Requisition Restriction Based on AOR (Doc ID 2540349.1)"

The recruiter is able to view requisitions in his Primary Location as indicated in his AOR. However when he wants to create a new requisition, He is able to create requisitions for other Primary Locations.

The recruiter is expected to create new requisitions for only the Locations indicated in his AOR.


Version (include the version you are using, if applicable):

Howdy, Stranger!

Log In

To view full details, sign in.

Register

Don't have an account? Click here to get started!