Staff console
This page is for Learn.GT staff. Learners and partners do not see the console.
Access
Section titled “Access”Staff sign in at the staff portal (/admin/login). Anyone who is not staff is redirected to the learner dashboard. The roles are:
| Role | Access |
|---|---|
| user | Learner. No console. |
| instructor | Staff with limited access. Cannot see platform-wide user data. |
| admin | Staff with platform-wide data. |
| superadmin | Everything admins can do, plus changing roles, plans and suspensions. |
The owner is the platform’s founding account. Further rules protect it and keep roles safe:
- Only a SuperAdmin can change a role, a plan tier or suspend an account.
- Only the owner can grant or take away SuperAdmin.
- The owner account cannot be changed or suspended by anyone else, and nobody can change their own role or suspend themselves.
- A role must be one of the four above and a plan one of free, pro or architect; anything else is refused.
- Staff accounts created by an administrator need a temporary password of at least 15 characters.
What is in the console
Section titled “What is in the console”| Page | What you do there |
|---|---|
| Platform Control Center | Global user management and analytics, with a shortcut to the payment provider’s dashboard. |
| Admissions | Review applications from prospective students for premium cohorts; open an applicant’s profile. |
| Academic Partners | See lecturers and institutions running classes, with their student counts. Verify or suspend partner accounts. A new application arrives with a flag showing whether the address was verified automatically or needs checking. A suspended partner cannot create classes. |
| Organizations | Create an organization for a school, university or company: give the owner’s email (they must already have an account), the plan the seats grant, and when the licence ends. Edit licence after an invoice is paid. Seated learners get the licensed plan until it ends. |
| Capstone grading | Download a learner’s .zip, work through the rubric by choosing a level for each criterion, and write feedback. The score and pass or return decision are calculated from your choices. Submissions are shown oldest first, with recently graded work below. |
| Submissions and grading | Review student coursework from classes, give grades and feedback. |
| Coupons | Generate percentage-off codes with a maximum number of uses and an optional expiry date. A code works once per account, on one-time payments, and not on auto-renewing subscriptions. |
| Events | Schedule live cohort sessions, Q&As and guest lectures with a meeting link (Zoom or Meet), start time and optional end time. |
| Support inbox | Read and answer student tickets across all cohorts. |
| Institution enquiries | Messages from the “Talk to us” form on the Institutions page. Reply by email, then mark the enquiry contacted. |
| Course interest | A count of visitors who said they would buy a course on its own. It is a demand test: nothing was charged and no price was shown. |
| Audit log | An immutable record of critical administrative actions and system events, with an Export Log button. |
Good practice
Section titled “Good practice”- Check a partner’s institution before verifying them; applicants who typed their institution by hand rather than choosing it from the list are flagged for a closer look.
- Grade capstones against the rubric levels, not by overall impression, so scores stay consistent between graders.
- Set an organization’s licence only after the invoice is paid.