Skip to main content
Solved

Referral Filtering

  • November 6, 2024
  • 1 reply
  • 18 views

  • Participating Frequently

Is it possible to filter a req folder by all referrals, not just new referrals (under the Views dropdown). The problem is when a new referral is advanced in the process they no longer appear in the new referrals filter and recruiters lose sight of them. It could be added as a filter or as a Highlights selection.

 

Using the filter of source = does not work for us the way our referral program is set up, unfortunately.

Best answer by dkreiger

Hi ​@kfayer7, Excuse us for the very lengthly wait here. 
 

Yes,  this is possible, but it requires adding/configuring a new pipeline “step” (view) in the Position Pipeline/Workflow config so that you have an “All Referrals” view, not just “New Referrals.” The reason you’re seeing the behavior you described is that the out‑of‑box New Referrals view is typically defined as “referred for this req” and “still in the New stage,” so once a referred candidate is advanced, they no longer match that view. 

 

Why “New Referrals” loses visibility after stage movement

In the pipeline configuration example, New Referrals is filtered using:

  • referred_for = "{{position.get_ats_job_id_int()}}" (the req) and
  • stage_map = new_applicant (still in the “New” stage group)

So advancing them removes them from “New Referrals.”

 

What to do instead: add an “All Referrals” view/step (recommended)

Pipeline “Views” are implemented as configurable Steps (pre-configured queries) in the workflow JSON/config.

To create an “All Referrals” step, you’d define a step that filters on “is a referral for this req” but does not include the stage_map = new_applicant condition. (That’s the key change.) 

 

Conceptually, it would look like:

  • Include: referred_for = "{{position.get_ats_job_id_int()}}" 
  • Keep whatever “active/exclude hired” logic you want (the New Referrals example includes application_status=active and excludes hired). 
  • Do not include stage_map = new_applicant. 

This gives recruiters a stable “All Referrals” bucket they can return to even after candidates move forward.

 

If you’re using “Referrals Requiring Candidate Application”

If your instance uses that feature, the docs also describe optional pipeline steps you can add, such as:

  • Referral Leads (referred but haven’t applied yet) using referred_for and excluding referred_applied_for 
  • Referral Applicants (referral applications) using referred_applied_for 

Depending on your process, one of these (or both) may already provide the “all referrals” visibility you want—just split by “applied vs not applied.” 

 

About doing this as a “Highlight”

In the pipeline, “Highlights/Traits” are available as filters/facets, but they’re meant for inferred traits (for example, Strong Career Growth, Top School, etc.). The “New Referrals” behavior you’re describing is specifically controlled by the Step/View definition (filters), so the most reliable fix is adding an “All Referrals” step/view. 

1 reply

dkreiger
Community Manager
  • Community Manager
  • Answer
  • March 18, 2026

Hi ​@kfayer7, Excuse us for the very lengthly wait here. 
 

Yes,  this is possible, but it requires adding/configuring a new pipeline “step” (view) in the Position Pipeline/Workflow config so that you have an “All Referrals” view, not just “New Referrals.” The reason you’re seeing the behavior you described is that the out‑of‑box New Referrals view is typically defined as “referred for this req” and “still in the New stage,” so once a referred candidate is advanced, they no longer match that view. 

 

Why “New Referrals” loses visibility after stage movement

In the pipeline configuration example, New Referrals is filtered using:

  • referred_for = "{{position.get_ats_job_id_int()}}" (the req) and
  • stage_map = new_applicant (still in the “New” stage group)

So advancing them removes them from “New Referrals.”

 

What to do instead: add an “All Referrals” view/step (recommended)

Pipeline “Views” are implemented as configurable Steps (pre-configured queries) in the workflow JSON/config.

To create an “All Referrals” step, you’d define a step that filters on “is a referral for this req” but does not include the stage_map = new_applicant condition. (That’s the key change.) 

 

Conceptually, it would look like:

  • Include: referred_for = "{{position.get_ats_job_id_int()}}" 
  • Keep whatever “active/exclude hired” logic you want (the New Referrals example includes application_status=active and excludes hired). 
  • Do not include stage_map = new_applicant. 

This gives recruiters a stable “All Referrals” bucket they can return to even after candidates move forward.

 

If you’re using “Referrals Requiring Candidate Application”

If your instance uses that feature, the docs also describe optional pipeline steps you can add, such as:

  • Referral Leads (referred but haven’t applied yet) using referred_for and excluding referred_applied_for 
  • Referral Applicants (referral applications) using referred_applied_for 

Depending on your process, one of these (or both) may already provide the “all referrals” visibility you want—just split by “applied vs not applied.” 

 

About doing this as a “Highlight”

In the pipeline, “Highlights/Traits” are available as filters/facets, but they’re meant for inferred traits (for example, Strong Career Growth, Top School, etc.). The “New Referrals” behavior you’re describing is specifically controlled by the Step/View definition (filters), so the most reliable fix is adding an “All Referrals” step/view.Â