Skip to main content
Solved

What type of reporting exists for mentorship?

  • August 21, 2026
  • 1 reply
  • 4 views

What type of reporting exists for mentorship? Are we able to pull reports to see how many mentors or mentees a certain individual has?

Best answer by dkreiger

Hi ​@beth.steffens

 

1) Data Hub (most flexible / “raw” reporting)

Mentorship relationships can be reported via Data Hub tables that track profile connections (mentorship connections, status, timestamps, etc.). In the S&P Global example, Support specifically pointed to the spglobal_profile_connection table as the source for mentorship reporting.

Data Hub can support:

  • Relationship-level reporting (mentor <--> mentee pairs, status, created/accepted/ended dates) via joins between the connection table and employee/profile tables.
  • Aggregations like “count of mentees per mentor” and “count of mentors per mentee.”
  • A quick validation query to confirm whether mentorship data exists in the connection table (e.g., SELECT COUNT(*) ...).


Separately, an internal ER confirmed that being able to download a full list of mentors / opted-in mentors is available through Data Hub.
 

2) In-product TM Feature Usage & Outcomes dashboard (Networking tab)

There are also in-product analytics for mentoring in the TM Feature Usage & Outcomes dashboard, specifically on the Networking tab, including metrics like employees open to mentoring and connection request activity.
 

3) Admin / program monitoring dashboards (product direction / materials)

The Mentorship materials position a Talent Management Admin dashboard for tracking mentorship usage and outcomes as part of “Measuring Success.”
 

Can we pull reports showing how many mentors/mentees a specific individual has?

Yes—Data Hub can be used to report both directions:

  • How many mentees a given mentor has (count mentee profile IDs grouped by mentor).
  • How many mentors a given mentee has (count mentor profile IDs grouped by mentee).


Support even provided sample SQL patterns for both counts (mentor-centric and mentee-centric) using the connection table joined to the employee table, grouped by the individual.
 

One practical caveat

If mentorship has been enabled but no mentorship connections have been created yet, the underlying connection table can be empty—so your queries will return no results until data exists.

1 reply

dkreiger
Community Manager
  • Community Manager
  • Answer
  • August 21, 2026

Hi ​@beth.steffens

 

1) Data Hub (most flexible / “raw” reporting)

Mentorship relationships can be reported via Data Hub tables that track profile connections (mentorship connections, status, timestamps, etc.). In the S&P Global example, Support specifically pointed to the spglobal_profile_connection table as the source for mentorship reporting.

Data Hub can support:

  • Relationship-level reporting (mentor <--> mentee pairs, status, created/accepted/ended dates) via joins between the connection table and employee/profile tables.
  • Aggregations like “count of mentees per mentor” and “count of mentors per mentee.”
  • A quick validation query to confirm whether mentorship data exists in the connection table (e.g., SELECT COUNT(*) ...).


Separately, an internal ER confirmed that being able to download a full list of mentors / opted-in mentors is available through Data Hub.
 

2) In-product TM Feature Usage & Outcomes dashboard (Networking tab)

There are also in-product analytics for mentoring in the TM Feature Usage & Outcomes dashboard, specifically on the Networking tab, including metrics like employees open to mentoring and connection request activity.
 

3) Admin / program monitoring dashboards (product direction / materials)

The Mentorship materials position a Talent Management Admin dashboard for tracking mentorship usage and outcomes as part of “Measuring Success.”
 

Can we pull reports showing how many mentors/mentees a specific individual has?

Yes—Data Hub can be used to report both directions:

  • How many mentees a given mentor has (count mentee profile IDs grouped by mentor).
  • How many mentors a given mentee has (count mentor profile IDs grouped by mentee).


Support even provided sample SQL patterns for both counts (mentor-centric and mentee-centric) using the connection table joined to the employee table, grouped by the individual.
 

One practical caveat

If mentorship has been enabled but no mentorship connections have been created yet, the underlying connection table can be empty—so your queries will return no results until data exists.