Admin Reference
Everything an admin can reach, in one place. Admins see an Admin link in the app header.
The dashboard
| URL | What's there |
|---|---|
/admin/ |
Overview: course/group/user/maintainer counts, recent activity |
/admin/courses |
One card per course — add and remove maintainers by email |
/admin/groups |
Create groups, bulk-add members by email, assign courses (with optional due date), unassign, delete |
/admin/audit |
The audit log: the 200 most recent changes — who, what, when, with links to the changed thing |
Adding a maintainer or group member by an unknown email creates the account immediately (invite-before-login); the person is matched on their first GitHub login.
Teacher views outside /admin
These need course-edit access (admin or that course's maintainer):
| URL | What's there |
|---|---|
/p/<problem-id>/manage |
Problem settings + file sidebar (editing) |
/p/<problem-id>/<file-id>/edit |
A file in the Monaco editor |
/p/<problem-id>/users |
Submission roster for the problem |
/p/<problem-id>/users/<user-id> |
One student's full history on the problem |
/page/<page-id>/edit |
Edit a content page |
Right-clicking entries in the course sidebar gets you to manage/users/edit without remembering URLs.
Things only the assistant (or SQL) can do today
Creating and deleting courses has no form UI yet — admins do it through the assistant in one sentence, or directly in the database. See Roadmap & limitations.
The audit log records…
Every file save, rename, and delete; problem settings changes; page edits; everything the assistant does (marked "AI … prompted by user"). If a maintainer asks "what changed?", the answer is at /admin/audit.