Skip to main content

Assessments and integrity

This page covers the admin side of learning and competing: the reports users file about content, the tools for reviewing suspected cheating, the queue of learners' proof of work, cohorts, and the accreditation reports built from all of it.

By the end of it you will know what each queue expects of you and, just as important, what each decision does and does not do.

Reports and moderation

Admin Panel → Evaluation & Arena → Reports (/admin/reports), headed "Reports & Moderation".

One page, five tabs. Each tab shows its pending count, a status filter (Pending, Resolved, All), and checkboxes so you can act on several rows at once. Only removing, deleting and confirming ask for confirmation; everything else applies straight away.

The tab strip with pending counts on each tab, the Pending / Resolved / All filter, and a few quiz report rows with the bulk action buttons above them.
TabWhat is reportedYour actions
Quiz ReportsQuizzes with inaccurate questions or answers, wrong options, or broken formattingDismiss marks the report as checked. Remove hides the quiz from users. Restore makes it available again.
Code Arena IssuesBroken Code Arena problemsResolve or Reopen
Cheat DetectionSubmissions flagged for reviewClear, Confirm, Reopen. See The review queue.
Message ReportsChat messagesDismiss, Delete, Reopen. See Community and learning.
Discussion ReportsPosts, answers and commentsDismiss. Remove takes the content down and closes every report on it. Reopen.

The sidebar links straight to Quiz Reports, Code Arena Issues, the cheat-detection tab (Flagged Submissions) and Message Reports. Discussion Reports is reached from the tab strip.

Reporters and authors are not notified of your decision.

Shortcuts outside the panel. Admins see a quiz-report dropdown with a count in the top bar. Admins and moderators see the shield review queue icon, which lists the latest open discussion reports. Moderators cannot open this admin page, so they act on reported content where it appears on the site instead.

Cheat detection

Check with your engineering team before relying on live scoring

Whether Code Arena submissions are scored automatically as they arrive is set by your engineering team, not by this page. Confirm with them before you tell learners that submissions are being checked. The page's On/Off switch and status badge do not decide it on their own.

The tools below work either way: replay how code was typed, test detection settings against real submissions, and review anything a staff-run review has flagged.

Admin Panel → Evaluation & Arena → Cheat Detection, headed "Cheat Detection Configuration". The sidebar entries are Flagged Submissions (the review queue), Overview & Stats, Configuration, Profiles and Simulator & Replay.

What the page does today

TabUse it to
PlayerReplay a submission step by step: how the code grew, when it was saved, where it jumped. Pick by user, problem and language, or browse. This is the most useful tool when someone disputes a result.
SimulatorRun the detector against real submissions using any profile, to see what it would flag. A dry run: it changes nothing and nobody is told.
OverviewTotals for flagged and pending submissions and the spread of confidence, plus recent detections
ProfilesNamed sets of settings. Create one by cloning an existing profile, and choose which is active.
Thresholds, WeightsThe detector's sensitivity, by signal
NotificationsThe message for each confidence level and the reward-blocked message
GuideHelp text on the page

At the category level, the detector looks for patterns such as large pastes, typing faster than a person can, too few saves for the problem's difficulty, suspiciously quick solves, a complete solution appearing at once, and close similarity to the reference solution. The exact settings are deliberately not documented.

What the switch and profiles affect. The master On/Off switch and the active profile shape the Simulator and staff-run reviews. Changing the active profile applies immediately, with no confirmation. Some settings, including the action chosen for each confidence level, are saved but not yet used by anything.

Saves appear in Config (Advanced) → Edit History. Changes saved while the built-in default profile is active may be replaced by the next platform update; save your own profile with Save As instead.

The review queue

Flagged Submissions opens the Cheat Detection tab on the Reports page. Rows appear here when a staff-run review of past submissions flags them; that review is run by your engineering team and is not scheduled.

Each row shows the user, problem, confidence, the signals that fired, the time taken, how many saves there were, and when it was detected.

ActionWhat it records
ClearNot cheating
ConfirmCheating (asks for confirmation)
ReopenBack to pending
Confirm records a verdict and nothing else

Confirm does not remove the user's Zeal or Jolt, does not notify them, and does not change any leaderboard. If a penalty is warranted, ask your engineering team; they can reverse rewards as part of a staff-run review.

Before confirming, open the submission in the Player. A flag is a reason to look, not proof.

How the platform keeps competition fair, as users see it, is on Fair play.

Proof Evaluation

Admin Panel → Education → Proof Evaluation (/admin/evaluation)

When learners mark a roadmap milestone, checkpoint or project as done, they attest that the work is theirs and can attach evidence: PDFs or links. Those declarations queue here.

The threshold field

The Pass threshold field, despite its label and hint, is not a score a proof must reach. It sets what share of a learner's roadmap progress depends on evidence. Declaring every item without evidence gets a learner the rest of the way; attaching the required evidence unlocks the final share. Raise it to make evidence matter more.

On some platforms this value is fixed by the server, so a change here may not take effect. If learners' progress does not change after you save, ask whoever runs the server.

Reviewing

The stats show Total, Pending, In Review, Passed and Failed. Filter by status and by type (Milestone, Checkpoint, Project), then Filter or Reset.

Each row shows the student, the item, its type, where it came from, the evidence and its evaluation status. PDFs open through a temporary link.

From the row menu:

ActionRecords
AcceptPassed
RejectFailed, with an optional reason
SkipSkipped

None of these ask for confirmation.

Learners are not told in this release

The learner is not notified of your decision and cannot see it. If a verdict matters to them, tell them directly.

Cohorts

Admin Panel → Education → Cohorts (/admin/cohorts), headed "Cohort Management".

A cohort is a group of students, such as a class or a batch, that you want to track together.

Summary cards show Total Cohorts, Active, Expired and Total Students. The table lists each cohort's name, faculty, students, achievements, status and expiry.

1. Create a cohort

Click New Cohort (or Create Cohort in the sidebar) and enter Cohort Name, Expires On and Description.

2. Add people

Open the cohort. Under Students, use Add Student with each student's email. Under Faculty, add the staff responsible.

Removing a member has no confirmation

The remove icon next to a student or faculty member acts at once.

3. Track progress

The cohort page shows:

  • totals for students, challenges, quizzes, Code Arena, labs deployed and more
  • an activity timeline over 7 days, 30 days, 90 days or a year
  • skills and tags touched, by CTF, quiz and code
  • top labs deployed, engagement, and a Student Leaderboard with Zeal, Jolt, CTF, quiz and code figures and when each student was last active

Cohorts cannot be renamed, re-dated or deleted from the panel in this release, and the achievements figures on cohort pages are not tracked yet.

Accreditation Evidence

Admin Panel → Education → Accreditation Evidence (/admin/accreditation-evidence)

Builds evidence reports for NAAC, NBA and NEP compliance from what happened on the platform.

  1. Choose an academic year (the last six are offered) or a Custom Date Range.
  2. Pick a report: Platform Summary, Lab Utilisation, Student Outcomes, Infrastructure, CTF & Cyber Labs, Learning & Pedagogy, Student Engagement or Code Analytics.
  3. Download it with Export PDF or Export CSV.

Reports work for admins. The page is also listed for faculty, but faculty cannot generate reports in this release.

Next