Skip to main content
Solved

How to Enable a Consolidated Dashboard for Recruiter-Wise Candidate Submission Tracking

  • Nov 17, 2026 11:02 AM UTC
  • 3 replies
  • 14 views

Forum|alt.badge.img+2

Team - I would like to understand how we can enable a consolidated dashboard in Eightfold to help recruiters track the status of all candidates they have uploaded or submitted into the system.

Currently, recruiters need to search for each candidate individually to identify their application status and progress. Having a consolidated view would significantly improve visibility and eliminate the need for repetitive candidate-level searches.

  • Does Eightfold provide any out-of-the-box dashboard, report, or configuration to achieve this

  • Can this be enabled through Candidate Database View, Application Analytics, or any existing reporting functionality

  • Is it possible to configure a recruiter-specific submission dashboard with candidate-level details and real-time application stage tracking

Best answer by dkreiger

Hi ​@apathiala , There isn’t a single out-of-the-box view today that shows “every candidate I uploaded or submitted, with their current stage.” The best way to get there is a custom Native Dashboard built for recruiters. Here’s how the options compare and what we’d recommend.

Where the existing tools fit

  • Recruiter Operational Dashboard: A good starting point, but it’s organized around positions (your reqs, pipeline metrics, stage progression, hires), not around the candidates you personally brought in.
  • Talent → Candidates: Great for finding and segmenting profiles, but it isn’t designed as a cross-requisition stage tracker filtered by who uploaded or submitted each candidate.
  • Application Analytics / Source Analytics: Strong for recruiter-level source and outcome reporting, including filters on who an application is credited to. It’s an aggregate view, though, not a candidate-by-candidate tracker.
  • Data Hub: A solid fallback if a scheduled report works for you. You can save a SQL query and have the results emailed as a CSV on a schedule.
  • Native Dashboards (recommended): An Admin or Admin (Analytics) can build a table from governed or custom SQL datasets, add filters and drill-downs, and share it with recruiters.

First, define “my candidates”

Eightfold tracks attribution in a few different ways, and they don’t always point to the same person:

  • Sourced by: who (or what) brought the profile into the system
  • Credited to: who gets credit for a specific application
  • Prospect owner at application time: available when prospect ownership is enabled

Before building, confirm which of these matches what your recruiters mean by “uploaded” and “submitted,” and check that it’s captured consistently across manual uploads, bulk imports and submissions.

Suggested dashboard: “My Uploaded and Submitted Candidates”

  • Main table (one row per application): candidate name/ID, requisition ID and title, attributed recruiter, application date, current status and stage, and last stage-change date. One row per application keeps things clear when a candidate is in several pipelines.
  • “Uploaded, not yet applied” section: so prospects without an application don’t drop out of view.
  • Filters: recruiter, upload/submission date, active vs. inactive, stage and requisition.
  • Summary tiles: total uploaded, total submitted, active applications, and applications by stage.

One note on access: a recruiter filter controls what’s shown, not what’s allowed. If each recruiter should see only their own candidates, set up Row-Level Security through user groups and access criteria.

How current will the stages be?

The newer analytics platform is near real-time, but how quickly a stage change appears also depends on when it reaches Eightfold from your ATS. Test it with a few candidates before you set expectations with recruiters.

Recommended next step

Have your Eightfold admin, working with your Solution Architect, check the attribution fields, stage data, refresh timing and access setup against a handful of real candidates. Then build the dashboard in Insights → Native Dashboards. Avoid starting a new legacy QuickSight customization for this.

If you go ahead with the build, please share how it goes here. Other recruiters have asked for the same thing.

View original

3 replies

dkreiger
Community Manager
Forum|alt.badge.img+3
  • Community Manager
  • Answer
  • Nov 18, 2026 6:01 PM UTC

Hi ​@apathiala , There isn’t a single out-of-the-box view today that shows “every candidate I uploaded or submitted, with their current stage.” The best way to get there is a custom Native Dashboard built for recruiters. Here’s how the options compare and what we’d recommend.

Where the existing tools fit

  • Recruiter Operational Dashboard: A good starting point, but it’s organized around positions (your reqs, pipeline metrics, stage progression, hires), not around the candidates you personally brought in.
  • Talent → Candidates: Great for finding and segmenting profiles, but it isn’t designed as a cross-requisition stage tracker filtered by who uploaded or submitted each candidate.
  • Application Analytics / Source Analytics: Strong for recruiter-level source and outcome reporting, including filters on who an application is credited to. It’s an aggregate view, though, not a candidate-by-candidate tracker.
  • Data Hub: A solid fallback if a scheduled report works for you. You can save a SQL query and have the results emailed as a CSV on a schedule.
  • Native Dashboards (recommended): An Admin or Admin (Analytics) can build a table from governed or custom SQL datasets, add filters and drill-downs, and share it with recruiters.

First, define “my candidates”

Eightfold tracks attribution in a few different ways, and they don’t always point to the same person:

  • Sourced by: who (or what) brought the profile into the system
  • Credited to: who gets credit for a specific application
  • Prospect owner at application time: available when prospect ownership is enabled

Before building, confirm which of these matches what your recruiters mean by “uploaded” and “submitted,” and check that it’s captured consistently across manual uploads, bulk imports and submissions.

Suggested dashboard: “My Uploaded and Submitted Candidates”

  • Main table (one row per application): candidate name/ID, requisition ID and title, attributed recruiter, application date, current status and stage, and last stage-change date. One row per application keeps things clear when a candidate is in several pipelines.
  • “Uploaded, not yet applied” section: so prospects without an application don’t drop out of view.
  • Filters: recruiter, upload/submission date, active vs. inactive, stage and requisition.
  • Summary tiles: total uploaded, total submitted, active applications, and applications by stage.

One note on access: a recruiter filter controls what’s shown, not what’s allowed. If each recruiter should see only their own candidates, set up Row-Level Security through user groups and access criteria.

How current will the stages be?

The newer analytics platform is near real-time, but how quickly a stage change appears also depends on when it reaches Eightfold from your ATS. Test it with a few candidates before you set expectations with recruiters.

Recommended next step

Have your Eightfold admin, working with your Solution Architect, check the attribution fields, stage data, refresh timing and access setup against a handful of real candidates. Then build the dashboard in Insights → Native Dashboards. Avoid starting a new legacy QuickSight customization for this.

If you go ahead with the build, please share how it goes here. Other recruiters have asked for the same thing.


Forum|alt.badge.img+2
  • Author
  • Trailblazer
  • Nov 19, 2026 5:28 AM UTC

Hi ​@dkreiger ,

Thank you for the detailed explanation and for outlining the available options.

The Native Dashboard approach seems to be a good solution for our requirement.

Our objective is to provide recruiters with a consolidated, recruiter-specific view of all candidates they have uploaded, sourced, or submitted across different requisitions, along with their latest application status and stage progression.

A few points we would like to clarify with the Eightfold team:

  1. Can the Native Dashboard capture candidates across all requisitions based on the recruiter who uploaded or submitted them?

  2. Can we differentiate between candidates uploaded to the database and candidates formally submitted against requisitions?

  3. Can the dashboard dynamically reflect the candidate's current application stage and status, including subsequent stage movements?

  4. Can recruiters access their respective candidate data through user-level access controls without requiring manual recruiter filters?

  5. Can we also include candidate-level details such as requisition ID, submission date, current stage, last stage update date, and application outcome?

We would prefer this as a standard recruiter operational dashboard rather than relying on individual searches or scheduled CSV reports.


dkreiger
Community Manager
Forum|alt.badge.img+3
  • Community Manager
  • Nov 20, 2026 5:00 PM UTC

Hi ​@apathiala , thanks for the detailed followup questions. Here is where each one stands:

1. Can a Native Dashboard capture candidates across all requisitions by recruiter?
Yes, as long as the dataset behind the dashboard includes a recruiter field. Recruiter is a standard breakdown (for example, Open Positions by Recruiter). One caveat: that field is usually the recruiter assigned to the requisition. We can’t yet confirm a standard field for the recruiter who uploaded or submitted a candidate. You can check what a widget includes through its Widget details or by exporting its raw data.

2. Can we tell uploaded candidates apart from formally submitted ones?
Yes. Eightfold treats these as different things:

  • Uploaded (database only): a profile created by résumé import, LinkedIn sourcing, or the Talent Network, with no application. Import tags and import history help identify these.
  • Lead: a candidate saved to a position’s Lead stage, who has not necessarily applied or been submitted.
  • Applicant: a requisition-specific application with its own status and history, managed in the Applicants pipeline.

For reporting, count uploads per candidate and submissions per application, since one person can have several applications. The exact filters depend on the configured workflow and ATS integration.

3. Can the dashboard reflect a candidate’s current stage and status as they move?
I can’t confirm this today for a consolidated, recruiter-level dashboard. The closest existing options are the Screening Dashboard and Global Search. The stage filters in Scheduling Center show the stage at the time the interview was created, not the candidate’s current stage.

4. Can recruiters see only their own candidates without applying a recruiter filter?
Filtering by recruiter is supported. Automatic user-level scoping, where each recruiter sees only their own candidates without a filter, is not confirmed.

5. Can we include requisition ID, submission date, current stage, last stage update date, and application outcome?
Availability of these fields in Native Dashboards hasn’t been confirmed yet. We’d recommend one row per application, so stages and outcomes don’t get mixed when a candidate is on multiple requisitions.