💡 Hidden Gem in Oracle Recruiting Cloud: Restrict Internal Job Postings Using Eligibility Profiles!

✨ Introduction

Ever wish you can show specific internal jobs to only a selected group of employees in Oracle Recruiting Cloud?

Most consultants overlook this powerful feature. But with Opportunity Marketplace Job Configurations and Eligibility Profiles, you can fine-tune internal job visibility—no need for role customisations or page composer hacks!

In this blog, we’ll show you how to control who sees what on the internal career site using this underused but highly impactful configuration.


🚀 Quick Setup – Enabling Job Segmentation

Before jumping into building the configuration, make sure your system is ready.

👉 Go to Setup and Maintenance → Search for Manage Administrator Profile Values → Enable this profile:

  • Name: Opportunity Marketplace Job Configurations Enabled
  • Code: ORA_HCM_OPP_MKT_JOB_CONFIG_ENABLED

With this switch turned on, you’re all set to create dynamic eligibility-based job visibility rules.


🧱 Step 1: Define Who Gets to See What

Let’s say you don’t want every employee to see every internal job. You want only those who’ve served 18 months or more to see certain roles. Here’s where Eligibility Profiles come into play.

This isn’t just a filter—it’s your first gatekeeper.

👣 What You’re Doing:

Creating a rule to group employees based on attributes like:

  • 🎓 Job Grade
  • 🏢 Department
  • 🌍 Location
  • 📅 Length of Service

🔧 How to Set It Up:

📍 Go to: Setup and Maintenance
Navigate to: Candidate Experience Management → Opportunity Marketplace Eligibility Profiles

➡️ Click Create > Create Participant Profile

  • Give it a name (e.g., “18Month_Eligibility”)
  • Under Profile Usage, choose Opportunity Marketplace
  • Under Eligibility Criteria, define: Length of Service ≥ 18 months

🛡️ Required Access: BEN_MANAGE_BENEFIT_ELIGIBLITY_PROFILE_PRIV

🎉 Done! You now have a rule that decides who’s allowed into your internal job club.


🎯 Step 2: Attach the Rule to Internal Jobs (Now with Visual Aid)

Now that you’ve decided who can see internal jobs, it’s time to define which jobs they can see.

This is where Job Configuration enters the scene.

🔧 What You’re Doing:

Linking your Eligibility Profile to job requisitions based on filters like job family or location.

👣 Steps to Follow (with Screenshot):

📍 Navigate to: Opportunity Marketplace Jobs Configurations

➡️ Click Create

  • Enter a Config Code (e.g., “ExecJobs_AD_Only”)
  • Give it a clear Name
  • Select the Eligibility Profile you just created
  • Add Requisition Filters:
    • Recruiting Type
    • Organization
    • Location
    • Job Family
    • Job Function

🛡️ Required Access: BEN_REST_SERVICE_ACCESS_BENEFITS_LOVS_PRIV

💡 When employees log in, Oracle applies the first active configuration that matches their profile—and only shows jobs that meet both requisition filters and eligibility criteria.

🎯 Real-World Scenario: Restricting Jobs to Employees who has worked for 18 months and above

Let’s take a real client example.

🧑‍💼 A customer approached us with a simple but critical demand:

“We want to show internal job postings only to employees who’ve been with us for 18 months or more.”

Why?

  • To ensure stability and reduce internal churn.
  • To reward loyalty and give growth opportunities to long-timers.

✅ So what did we do?

  • We created an Eligibility Profile with a service length condition (≥ 18 months).
  • Linked that profile to relevant requisition groups using Job Configurations.

🎯 Outcome: Only eligible employees saw the job postings. Others didn’t even know the requisitions existed.

No confusion. No complaints. Just clean, targeted internal mobility.

👥 Walk through with Screenshots

To show this in action, we’re showcasing two employees:

  • 👩‍💼 Employee A – Deirdre Ahern – with less than 18 months of service
  • 👨‍💼 Employee B – Aurora Reyes – with more than 18 months of service** – with more than 18 months of service

We’ve taken the same steps on both profiles and placed them side-by-side to highlight the visibility difference in the Opportunity Marketplace.

🖼️ Screenshot 1: Hire Date Comparison

Both employees with their hire dates visible—this confirms who meets the eligibility criteria.

🖼️ Screenshot 2: Homepage Comparison

View of each employee’s homepage side-by-side—note that everything looks identical at this point.

Side-by-side comparison of employee homepages for Deirdre Ahern and Aurora Reyes, with their names displayed and access options highlighted.
Click to Enlarge Images for Detailed Insight

🖼️ Screenshot 3: Opportunity Marketplace Dashboard

Both users navigate to the internal career site and see few requisitions are not visible

Side-by-side comparison of two Opportunity Marketplace job listings interface showing different job postings available to employees based on eligibility profiles.
Click to Enlarge Images for Detailed Insight

🖼️ Screenshot 4: Searching for a Specific Requisition

Now the twist! When both search for the same requisition:

  • ✅ Employee B (18+ months) sees the job listing
  • 🚫 Employee A (<18 months) doesn’t see it at all!
Screenshot showing the Opportunity Marketplace interface with two side-by-side views: one displaying 'No results were found' and the other showcasing a job listing for 'Charge Nurse' with relevant details.
Click to Enlarge Images for Detailed Insight

This visual walk-through clearly proves that the eligibility profile works exactly as expected. It shows control of internal visibility based on employee tenure.


🚧 Known Limitations (and Why We Raised an Idea!)

Even though this feature is incredibly useful, it’s not perfect. Here are two key challenges you should be aware of:

1️⃣ 🎯 Eligibility Can’t Be Applied at Individual Requisition Level

Let’s say you’ve got 10 jobs in the same family. You want 5 to be visible to everyone and 5 only to senior staff.

🚫 Not possible.

Oracle currently allows eligibility to be tied only to the job configuration level, which groups requisitions using filters—not one-by-one control.

2️⃣ 🙅‍♂️ Hidden Jobs Can’t Be Referred

Here’s the real twist:

If an employee isn’t eligible to view a job, they can’t refer anyone for it either. It’s invisible to them entirely.

📌 Which means: if a superstar employee knows someone perfect for the role, they won’t even be able to refer them if they don’t meet the eligibility.


✋ We Raised an Enhancement Request

We believe this feature needs two key upgrades:

  • ✅ Ability to apply eligibility at the requisition level
  • ✅ Allow referrals even if the job is hidden from the employee

📢 We’ve raised an enhancement request for this on Oracle Cloud Customer Connect.

🙏 Do you agree? Jump in and upvote the idea so Oracle knows it matters!


🧠 Final Takeaway

Using Eligibility Profiles + Opportunity Marketplace, you can:

🔐 Control who sees what job internally
🎯 Promote the right talent at the right time
🧼 Keep your security model clean and scalable

This feature is a hidden gem in Oracle Recruiting Cloud—simple to implement, but powerful in impact.

Don’t let it go unnoticed. Explore it. Use it. Share it.


Discover more from FusionPathfinder

Subscribe to get the latest posts sent to your email.

Leave a Reply

Categories

FusionPathfinder

Exploring Oracle Fusion HCM – Insights and Journeys in Tech Transformation

Discover more from FusionPathfinder

Subscribe now to keep reading and get access to the full archive.

Continue reading