ICIMS Internal Mobility Setup: A Consultant’s Guide
Certified ICIMS Implementation Partner

ICIMS Internal Mobility Setup, the consultant’s playbook.

How to configure Workflow Profiles, HCM field mapping, and Opportunity Marketplace so employees can actually find their next role inside your ICIMS instance.

Book a Free ICIMS Strategy Call β†’
9 min read Β· Updated August 2026

ICIMS internal mobility setup is the configuration work that decides whether your employees can actually see and apply to internal openings, or whether those openings quietly stay invisible to the people already inside your company. Get more from your ICIMS investment here, and you turn a platform that was built for external hiring into one that also keeps your best people from leaving for a job down the street.

We get asked about this constantly. Recruiting teams license ICIMS to fill external requisitions, and internal mobility ends up bolted on almost as an afterthought. That’s a missed opportunity. ICIMS supports internal mobility two different ways, and knowing which one fits your team (or how to combine both) is the first decision that shapes everything else.

The two paths: Workflow Profile vs. Opportunity Marketplace

There are two legitimate ways to run internal mobility inside ICIMS, and they are not mutually exclusive. The first path uses tools every ICIMS customer already has: a dedicated internal Workflow Profile, an internal career portal, and login group access. The second path is ICIMS Opportunity Marketplace, a licensed module built specifically for internal talent marketplaces, with AI-powered skills matching, a Mobility tab inside the ATS, and employee-facing career pathing.

Picture this: a mid-market manufacturer with 1,200 employees doesn’t need AI skills matching to get internal mobility working. A dedicated Workflow Profile, a clean internal portal, and sensible approval routing covers most of what they need. An enterprise TA team supporting 15,000 employees across a dozen business units is a different story. That’s where Opportunity Marketplace’s skills-based matching and Career Studio content start to earn their keep by surfacing roles employees would never have found on their own.

Before

Internal roles live in the same Workflow Profile as external requisitions

Employees never see the internal portal unless someone emails them a link

Internal hires get buried inside overall source reporting

After

Internal moves run through their own Workflow Profile with its own statuses

Employees find the internal portal through SSO from your intranet or HCM

Internal hire rate and time to fill are visible on their own dashboard

Mapping the Active Employee field to your HCM

If you’re implementing Opportunity Marketplace, this is the piece that has to happen first. ICIMS identifies internal candidates using the Active Employee field on the Global Person Profile, and that field needs to be part of your HCM integration so ICIMS knows who’s currently employed. Skip this step and Opportunity Marketplace has no reliable way to distinguish an employee from an external applicant.

Tip: Loop in your HRIS integration owner before you touch Opportunity Marketplace configuration. The Active Employee field mapping usually needs a small change on the Workday, UKG, or ADP side, and that conversation goes faster when it happens before implementation starts, not after go-live.

Once the Active Employee field is flowing correctly, ICIMS Talent Cloud AI can use current and previous job titles from that same Global Person Profile to suggest skills for an employee’s profile, and to surface roles that share skills with the ones they already have. None of that works without clean, current HCM data behind it.

Designing a dedicated internal Workflow Profile

Whether or not you license Opportunity Marketplace, a dedicated internal Workflow Profile is the foundation. It keeps internal transfer requisitions on their own statuses, forms, and disposition codes instead of sharing a profile built for external hiring, where the questions, approvals, and reporting rarely fit an internal move.

1
Create the profile. Build a Workflow Profile scoped specifically to internal transfer requisitions, separate from your standard external profiles.
2
Build internal-specific statuses. Add statuses that reflect an internal move (manager notified, internal interview, internal offer) instead of reusing external hiring statuses that don’t quite fit.
3
Set eligibility rules. Decide whether employees need to be in their current role for a minimum tenure before applying internally, and build that into the application form or a screening question.
4
Map it to the internal portal. Confirm the new Workflow Profile is included in your internal career portal’s display settings. This step gets missed more than any other, and we’ll come back to why.
5
Wire up approval routing. Configure the approval chain so an internal move doesn’t sit in a single manager’s queue for two weeks. More on this below.

This is the same discipline that goes into any well-built ICIMS onboarding setup: a workflow that matches the actual process, not a generic template stretched to cover a use case it wasn’t built for.

Internal career portal and login group access

An internal Workflow Profile is only useful if employees can actually find it. Most ICIMS customers build a separate internal career portal, distinct from the public-facing career site, and grant access to it through SSO from the company intranet or HCM system rather than a public login page.

Login Group Access

Employees get a login group scoped to the internal portal, separate from the login groups your recruiters and hiring managers use day to day.

Portal Display Mapping

The internal portal’s display settings must explicitly include the internal Workflow Profile, or approved internal postings stay invisible.

SSO From the Intranet

Linking the internal portal from your intranet or HCM homepage does more for adoption than any email announcement ever will.

This is the same failure pattern behind a lot of the tickets we see on the external side, covered in our guide to an ICIMS career site not showing jobs. Approving a requisition and posting it to a portal are two separate actions in ICIMS, and an internal Workflow Profile that was never added to the internal portal’s mapping will produce fully approved internal openings that no employee can see.

Configuring Opportunity Marketplace and skills matching

ICIMS Opportunity Marketplace adds a Mobility tab to the ATS along with a dedicated internal marketplace experience for employees. Once the Active Employee field is mapped correctly, ICIMS Talent Cloud AI generates skills recommendations for each employee’s profile based on their current and previous job titles, and identifies skills that commonly co-occur with the ones they already have. That powers one-click job recommendations employees see the moment they log in.

Opportunity Marketplace also includes Career Studio, a hub that helps employees prepare for roles that aren’t open yet, and Video Studio for Opportunity Marketplace, which lets current employees record short testimonial videos about their team or role. Those videos give job seekers a more honest picture of an internal move than a job description alone ever could, and they tend to get more attention from employees than another email newsletter.

None of that AI matching or content replaces the configuration work underneath it. Skills matching is only as good as the Global Person Profile data feeding it, and that traces straight back to the HCM integration and Workflow Profile decisions covered above.

Routing approvals: current manager and hiring manager

Internal moves involve two managers with a real stake in the outcome: the employee’s current manager and the hiring manager for the new role. ICIMS can route these approvals simultaneously rather than sequentially, so the request doesn’t stall for a week waiting on one manager before the other even sees it.

Simultaneous routing matters more here than almost anywhere else in the platform. A sequential chain that works fine for a standard hiring approval can quietly kill internal mobility, because a current manager who doesn’t want to lose a strong employee has every incentive to sit on the request. Building the approval logic to route to both managers at once keeps that dynamic from derailing the process. This same principle shows up in how we help teams configure an ICIMS hiring manager dashboard that actually drives adoption instead of getting ignored.

Get More From Your ICIMS Investment

We help mid-market and enterprise TA teams configure ICIMS internal mobility, from a single Workflow Profile to a full Opportunity Marketplace rollout.

Book a Free ICIMS Strategy Call β†’

Reporting on internal hires

Once internal moves run through their own Workflow Profile or Opportunity Marketplace, you have clean source and disposition data to report on. That’s the point where internal mobility stops being a talking point in a town hall and becomes a number leadership can track: internal hire rate, time to fill for internal moves, and mobility activity broken out by department or business unit.

Capability Workflow Profile Path Opportunity Marketplace
Internal portal with dedicated postingsYesYes
AI skills matching and job recommendationsNoYes
Employee testimonial video contentNoYes, via Video Studio
Simultaneous manager approval routingYesYes
Career pathing beyond currently open rolesNoYes, via Career Studio
Isolated internal hire reportingYesYes

If you’re already investing in an ICIMS analytics dashboard, add internal hire rate as its own tracked metric rather than letting it get folded into your overall source-of-hire report. Leadership tends to care a lot more about internal mobility once they can actually see the number.

5 configuration mistakes to avoid

1
Forgetting the portal mapping. A new internal Workflow Profile that isn’t added to the internal portal’s display settings produces postings nobody can see. This is the single most common gap we find during an ICIMS system audit.
2
Skipping the Active Employee field mapping. Without it, Opportunity Marketplace can’t reliably tell current employees apart from external applicants, and skills matching quality suffers.
3
Sequential approval routing. A current manager who doesn’t want to lose an employee can sit on a sequential request indefinitely. Simultaneous routing keeps the process moving.
4
No dedicated eligibility or tenure rules. Reusing external application forms for internal moves means you lose the chance to ask the questions that actually matter, like current tenure or manager notification status.
5
Letting internal hires disappear into general reporting. If internal mobility isn’t broken out as its own reporting category, leadership has no way to see whether the investment is working.

None of these are platform limitations. They’re configuration decisions, and every one of them is fixable without a re-implementation. We work alongside ICIMS Professional Services on exactly this kind of project through our ICIMS implementation consulting services, as a dedicated extension of the TA team.

FAQ

What is ICIMS internal mobility setup?
It’s the configuration work that lets current employees see and apply to internal openings inside ICIMS, either through a dedicated Workflow Profile and internal career portal, or through ICIMS Opportunity Marketplace, ICIMS’s internal talent marketplace module.
Do we need Opportunity Marketplace to support internal mobility in ICIMS?
No. Many ICIMS customers support internal mobility with a dedicated Workflow Profile, internal career portal, and login group access alone. Opportunity Marketplace adds AI-driven skills matching, career pathing, and employee video content on top of that foundation, but it is a separate licensed module.
What is the Active Employee field in ICIMS?
The Active Employee field lives on the ICIMS Global Person Profile and identifies a person as a current employee. Opportunity Marketplace implementations require this field to be mapped into your HCM integration so ICIMS can recognize internal candidates automatically.
Why isn’t our internal career portal showing internal transfer jobs?
This almost always traces back to portal display settings. Each ICIMS career portal is configured to show postings from specific Workflow Profiles. If a new internal-mobility Workflow Profile was never added to that mapping, the postings exist but stay invisible to employees.
How does approval routing work for internal moves in ICIMS?
ICIMS can route an internal transfer for simultaneous approval by both the employee’s current manager and the hiring manager for the new role, rather than a single sequential chain. This is configured in the Workflow Profile’s approval settings.
Can we track internal hires separately from external hires in ICIMS reporting?
Yes. Once internal moves flow through their own Workflow Profile or Opportunity Marketplace, source and disposition data lets you build reports and dashboards that isolate internal hire rate, time to fill for internal moves, and mobility by department.

Ready to Configure ICIMS Internal Mobility the Right Way?

Book a free strategy call and we’ll walk through what internal mobility setup looks like for your ICIMS instance.

Book a Free ICIMS Strategy Call β†’

Similar Posts