Overview & user management

The Programme admin area is your control centre for the whole CLIP Learn platform. This page covers two screens: the Overview dashboard you land on, and the Users screen where you manage every account. Both live under the top admin navigation and are reached at /admin and /admin/users.

The admin navigation

Every admin screen shares a header. The heading reads Programme admin for an ADMIN (subtitle "Learners, escalations and knowledge — self-service") and Team overview for a CORPORATE sponsor (subtitle "Your sponsored candidates at a glance"). The tab row is:

The MOEgent copilot panel appears at the bottom of every admin screen for ADMIN users only.

The Overview dashboard (ADMIN)

/admin opens on four KPI tiles, two charts, a noticeboard composer, an escalation queue and a live-activity feed. All figures are computed live on each page load. For an ADMIN the numbers cover the entire platform; for a CORPORATE sponsor they are silently limited to candidates in that sponsor's own organisation (see The Corporate sponsor view).

The four KPI tiles

Activity — last 14 days

A bar chart of questions answered per day over the trailing 14 calendar days (UTC), including today. Each bar's height is relative to the busiest day in the window; a day with at least one answer always shows a minimum sliver so it is visible. Hovering a bar shows a tooltip of the exact date and count in the form date: count. The caption beneath reads "N questions answered across the platform", where N is the total across all 14 days — this total and the bars count exactly the same events (both are ANSWER_SUBMITTED learning events since the start of the oldest visible day).

Weakest topics (avg mastery)

A ranked list of up to six topics with the lowest average mastery, drawn from learners' MasteryScore records. Only topics with at least one attempt are included.

• Each learner's mastery of a topic is an Elo-style rating that starts at 1000 and moves up or down as they answer questions on that topic. The dashboard shows the average rating across all learners for each topic, rounded to a whole number.
• Topics are sorted lowest rating first (weakest at the top) and the bottom six are shown. The bar length is scaled against a baseline of 1200, so a topic sitting near the starting 1000 shows as a short-to-medium bar.
• Empty state: if no learner has any mastery data yet, the panel reads "No mastery data yet."

Post to the noticeboard

A one-line composer that publishes an announcement to every learner's dashboard within the current tenant. ADMIN only — the panel is hidden for CORPORATE sponsors.

If either field is blank after trimming, nothing is posted. The announcement is attached to your tenant; if the system cannot resolve a tenant, the post is silently skipped. Posting is recorded in the audit log as an ANNOUNCE action (with the title in the log's metadata). New announcements are not pinned by default.

Learner questions for the team (escalation queue)

When MOEgent cannot answer a learner's question from the course materials, it opens an escalation ticket. Those open tickets land here so a human can close the loop. ADMIN only — the panel is hidden for CORPORATE sponsors (though the underlying reply action is open to FACULTY too, via the faculty screen).

The panel header shows a live count badge — "N waiting" — of tickets whose status is still OPEN, sorted newest first. Each ticket shows:

• The learner's question text.
• The learner's name and the time the ticket was created (YYYY-MM-DD HH:MM).
• A reply box.

When you send an answer, the ticket's status flips from OPEN to ANSWERED, your reply and your name are stored on the ticket, and a resolved-timestamp is set. A TICKET_ANSWERED learning event is recorded, and the action is written to the audit log as ANSWER_TICKET. The ticket then drops out of the "waiting" queue.

Empty state: when nothing is outstanding, the panel reads "Nothing waiting — every learner question has an answer."

Live activity

A rolling feed of the 12 most recent learning events across the platform — "the event spine: every lesson view, answer and chat, captured." Each row shows the actor's name (or System if the event has no user), the event verb in plain lower-case words (for example ANSWER_SUBMITTED renders as "answer submitted"), and the time of day (HH:MM, UTC). For a CORPORATE sponsor this feed widens to fill the row because the escalation queue beside it is hidden. Empty state: "No activity yet — it appears here as learners study."

The Corporate sponsor view

If you sign in with the CORPORATE role, /admin shows a dedicated Team readiness & ROI page instead of the admin dashboard above. It is scoped entirely to your own organisation's candidates — no platform-wide data, no escalations, no noticeboard. It contains:

• Your organisation's name and an Export CSV button (a client-side download — no data leaves the page to a server; spreadsheet-formula injection in names is neutralised).
• Four KPI tiles: Seats used (used / purchased), Cohort completion (average progress %), Exam-ready (ready of total), and Need support (highlighted when above zero).
• A Projected exam-readiness bar splitting your candidates into Exam-ready / On track / Needs support.
• A per-employee table: name, progress, accuracy, best mock score, target sitting, a readiness badge and last-active date.

Each candidate's readiness is derived automatically:

Empty state: "No sponsored candidates yet."

User management (ADMIN)

/admin/users is the master list of every account on the platform. ADMIN only. From here you filter and search accounts, change roles, suspend or restore access, edit contact details, and reset passwords. Every one of these changes is written to the append-only audit log (see Audit logging).

Filtering and searching

Above the table sits a row of role filter chips and a search box:

• All (N) plus one chip per role — ADMIN, FACULTY, CORPORATE, CANDIDATE — each showing a live count. The active chip is highlighted. Clicking a chip filters the table to that role via ?role=….
• A search box ("Search name / email…") matches on name or email, case-insensitively, on a partial match. It preserves the current role filter. Submit by pressing Enter.

The table shows at most 200 users, newest account first. If more than 200 match, narrow with a role filter or search.

The user table

Change a user's role

The four roles mean:

Suspend or restore a user

The Status button is a one-click toggle:

Suspending sets the account's active flag to false and is logged as SUSPEND_USER; restoring sets it back to true and is logged as RESTORE_USER.

Edit a user's details

If Name or Email is empty after trimming, the save is ignored. If the new email is already in use by another account, the save is silently refused (the email is not changed) — there is no on-screen error, so if an edit appears not to take, check for a duplicate email.

Reset a user's password

The Reset password button generates a fresh temporary password and shows it to you once.

Details and edge cases:

• The temporary password has the form Clip- followed by a short random string and two digits (for example Clip-a4f9k57). It is shown only once — it is not stored in readable form and cannot be retrieved again. If you lose it, reset again.
• Resetting a password immediately deletes every active session for that user, so any old password (and any logged-in device) stops working at once.
• The reset is recorded as RESET_PASSWORD in the audit log.
• It only works for password (email/credential) accounts. If the user signs in with Google (or any other social provider) and has no password credential, the button shows "Failed — retry" — there is no password to reset. Direct such users to sign in with their provider instead.

Audit logging

Every privileged change described on this page is appended to an immutable audit log, viewable by an ADMIN at /admin/audit. This exists because CLIP Learn is a regulated certificate issuer: roles, suspensions, answers and announcements cannot be changed silently.

Each entry records when, who (the acting admin's email, or a short id if no email), what action, and the target. The most recent 200 entries are shown, newest first. Audit entries reference the target by id rather than a hard link, so they survive even if the user or ticket is later deleted. The actions logged from the screens above are: