Skip to content

The Portal — Mentor side

A mentor signs in with the same magic link as everyone else, and the Portal takes them to /staff, a three-page view scoped to their own cohorts only.

The welcome page. It greets the mentor by first name — “Good afternoon, Chip” — names the cohorts they mentor underneath, and then shows four pieces of information:

  • Needs you first. The submissions waiting on them, up to four shown here with a link to see all. Each row says what the assignment is, who submitted it, how long ago it arrived, and a Pill: either Submitted in a quiet tone, or 3d late in clay if the submission arrived past its due date.
  • Group pulse. Up to six students on the mentor’s roster, each with a progress bar of contact hours against the number required by graduation. The students with the fewest hours surface first. Each bar’s color follows standing: sage for on pace, clay for behind.
  • Next session. The mentor’s next intensive or cohort call, with the Kanuga room and the Zoom link where applicable.
  • Your cohorts. The list of cohorts assigned, with the number of students in each.

A one-sentence lede at the top summarizes the day in words: “3 submissions are waiting on you. One of them is past due. Next up: the January intensive, Jan 7–11.”

A full roster of the mentor’s cohort. If they mentor more than one, tabs at the top let them switch. For each student:

  • Name, email, format (in person or virtual).
  • Contact hours against the required.
  • Pending submissions count.
  • Standing badge: On pace, Watch, Behind. The sort order puts the Behind rows first.

Mentors see their own cohorts only. Row-level security on the database prevents a mentor from reading another mentor’s students, no matter where in the app they look.

The deep-focus page. One table of every submission waiting on this mentor, sorted by how long ago it arrived. Each row has the submission, the student, when it arrived (and a d late pill where applicable), and a Review button.

The Review drawer opens from the right side, with the submission’s file and a few actions:

  • Accept. The submission is marked accepted; the student sees it move from Submitted to Accepted on their Homebase.
  • Return with feedback. A text box opens; the mentor’s note goes back to the student, who sees the assignment move back to open with feedback attached.
  • Attach a file. For when the mentor wants to send a marked-up copy.

Every action writes to the student’s Timeline back in the CRM, so the office sees the mentor’s work alongside everything else.

  • Mentors do not see tuition. That belongs to the office.
  • Mentors do not see other mentors’ students.
  • Mentors cannot invite anyone or change anyone’s role. That is a Team page function.

Next: The pipeline model.