PIP

The console is not connected yet.

This page needs the Supabase details before anyone can sign in.

What to do

1. Open config-global.js and fill in SUPABASE_URL and SUPABASE_KEY.

2. Use the same two values that are already in config.js. One source of truth, two shapes.

3. Your staff account must be listed in ns_staff before it can read anything here.

Full steps are in SETUP.md.

PIP

Admin sign in

Staff only. Learners never come to this page.

You stay signed in only for this browser tab. Close the tab and you are signed out.

edureka PIP admin

Enrol learners

Type one named learner per line as Name | email. Every enrolment requires a valid email address.

Blank lines are ignored. Names can repeat; the codes are always different. Use “ | ” between a name and email.

Used to group and filter the roster. It can be left blank.

Working...

Copy these now. Codes are shown in the roster too, but this is the moment to save them.
NameEmailCodePlay linkCohort
Show as plain text (select and copy by hand)

Roster

Everyone who has a code. Click a name to see what they have done.

—

Code Name Cohort Who they are Status World / lesson Lessons done Time played Last seen Actions

Who they are — what they told PIP before their first lesson

Lesson by lesson

Lesson Starts Runs that stopped Passes Time First Last
No lesson activity yet.

Saved progress

What happened

    No activity yet.

    Overview

    Where people are, and where they get stuck.

    Lesson funnel — reached, passed, and how many stopped there

    Passed Reached but not passed
    Lesson World Reached Passed Drop-off Pass rate Bar
    No activity yet.

    A pass rate is shown only when at least 5 people reached that lesson. Below that the counts are too few to mean anything, so a dash is shown instead.

    Hardest lessons — most runs that stopped

    LessonRuns that stoppedLearnersBar
    No stopped runs recorded yet.

    What stopped the run — what Python said most often

    What happenedRaw nameTimes seenBar
    Nothing recorded yet.

    Learners

    What the class told PIP before their first lesson. Everyone with a code is counted. These answers are not split by cohort.

    Where they are starting from — read from the two Python screens

    Starting pointLearnersShareBar
    No answers yet.

    Have they tried to learn before

    AnswerLearnersShareBar
    No answers yet.

    What worries them — they could tap more than one

    WorryLearnersShareBar
    No answers yet.

    One person could tap several worries, so these shares do not add up to 100%. A share is shown only once at least 5 people have answered the questions.

    How they type

    AnswerLearnersShareBar
    No answers yet.

    Why they are here

    AnswerLearnersShareBar
    No answers yet.

    Feedback

    What learners sent from inside the game. Click a row to read the whole report, including the picture of their screen.

    —

    When Who Kind What they said Status

    Who they are — what they told PIP before their first lesson

    The picture — their screen when they wrote to us

    What they said

    Staff note — only staff see this

    Everything in this report

    The last steps before they wrote — newest first

    WhenWhat happenedRaw
    No steps came with this report.

    What the browser itself reported — technical, for a developer

    MessageWhereWhen
    The browser did not report any trouble.
    Show the whole report as text