Proof records require manual review before any access action.
Review ProofPending
Purposeful preparation for British-curriculum and global students.
Sign Up
Admin Portal
Review access, teachers, and content in one place
Admins manage student approvals, payment verification, Access Grants, teacher applications, content review, live-session visibility, and platform publishing decisions.
Static admin preview. Real permissions, audit trails, and secure backend logic are not implemented yet.
Admin overview
Operational status without fake analytics clutter
These illustrative counts show how admin work can be grouped around review queues and controlled access decisions.
Student requests need pathway and target checks.
Under ReviewApplications require profile and document review.
PendingTeacher content must be approved before publishing.
Review ContentUnder ReviewVisibility and join timing require controlled release.
Create SessionApprovedCurrent active grants control protected content access.
Manage GrantsActiveReview queue
Safe summaries for sensitive admin work
Queue cards should show enough context to act, without exposing payment proof images, private documents, or unnecessary personal details in the list view.
Payment proof reviewCourse access request
Proof metadata has been submitted for a Mathematics course target. Private file preview is not shown in the queue.
PendingReview
Student access requestExam Room access
Student has requested timed mock access for an approved pathway. Access scope needs confirmation.
Under ReviewReview
Teacher applicationSubject and pathway review
Applicant supports IELTS Academic Writing and Academic Skills. Public visibility is not approved yet.
Pending
Teacher content approvalPower Notes pack
Teacher-submitted Power Notes need review for accuracy, syllabus fit, and brand quality.
Under Review
Course visibility reviewPublic course card
Course page is ready for final visibility check before public display.
Needs Info
Assignment Guidance requestIntegrity review
Request must be checked for guidance-only support and academic integrity before assignment to a reviewer.
Under Review
Access Grants
Access is granted by target, not by proof alone
The real admin portal must make course, resource, pathway, Exam Room, bundle, and expiry scope explicit before access is created.
Grant course access
Release approved lessons and linked modules for a specific course target.
Manage GrantsGrant resource access
Release view-only Power Notes, Past Paper Bank, or Explained Solutions where approved.
Grant Exam Room access
Allow approved quizzes, mocks, and result views for a selected scope.
Revoke/expire access
Lock content again when a grant is expired, revoked, or no longer valid.
View-only content rule
Protected study content stays view-only unless download access is explicitly approved.
Control rule
Payment proof must not unlock content automatically
Proof review can support an admin decision, but Access Grants are the only unlock model for protected content.
Access is granted by specific course, resource, pathway, bundle, or subscription target.
Payment proof alone does not unlock protected lessons, notes, or Exam Room content.
Protected study content should remain view-only unless explicitly approved.
Teacher and content approval
Public visibility and content approval stay separate
The admin portal should make it clear whether a teacher is approved, public, assigned, and whether submitted material is ready to publish.
Teacher profile review
Teacher status and public visibility require admin decision.
Teacher-submitted Power Notes
Accuracy, syllabus fit, and formatting need review before publishing.
Mock exam explanations
Solutions need clearer mark-scheme references before approval.
Live session material
Session slides and preparation notes are approved for use.
Public visibility approval
Only approved and public teacher profiles should appear on public pages.
Safety and audit
Sensitive admin actions need confirmation and history
Real admin workflows must protect private files, prevent accidental approvals, and record who changed important access, payment, teacher, and content states.
Sensitive actions require confirmation.
Destructive actions should not be one-click.
Approval history should be tracked in the backend.
Admin roles and permissions need secure backend implementation.
Admin preview
Keep operational control clear and accountable
The public website can show the platform direction, while the real admin portal must enforce permissions, audit trails, and secure review workflows.