Home/Documentation/Platform Admin
Guide 10 · For Simusim platform staff

Operating the platform with Platform Admin

The internal console for the Simusim team: onboarding schools, recording their payments, managing entitlements and suspensions, approving SMS sender names, curating family plans, and reading the audit trail. Schools never see this app — but what happens here decides what they see.

Internal · staff accounts only Roles: super-admin & support

§ 01Access & roles

Platform Admin is for Simusim staff accounts only (“Staff access — Sign in”). Two roles exist: super-admin (everything, including onboarding, suspensions, and payments) and support (read-mostly; destructive and money actions are gated). If you see “Your account is not authorized for the platform-admin app”, you're signed in with a non-staff account.

§ 02The dashboard

Four signals, refreshed on load:

  • In grace — schools past their paid period, inside the grace window. These need a decision soon.
  • Suspended — schools whose educational apps are currently blocked.
  • Email bounces (24h) — delivery problems worth chasing before they become “we never got the invite”.
  • Period ends (7d) — renewals due this week.

The Attention required panel lists every school in grace or suspended; This week shows upcoming period ends and audit signals (failed reminders, lockout spikes).

§ 03Onboarding a school (super-admin)

  1. Press Onboard school (dashboard or Schools list).
  2. School details: legal name, display name, the slug (3–40 chars, lowercase letters/digits/hyphens, starts with a letter — checked live for availability; this becomes login.simusim.com/<slug>), country, currency, and the code prefix (exactly 3 uppercase letters, e.g. KMP — it namespaces every student code).
  3. Initial admin: full name, email, optional phone. This person receives the welcome email and becomes the school's first administrator.
  4. Subscription & apps: trial length (1–90 days, default 14) and the checkbox list of enabled apps — all on by default; untick what they haven't bought.
  5. Press Onboard school. The success card confirms the school and shows the admin's credentials/invite state. Continue to the school's page.
Choose the slug carefully The slug ends up printed on every login card the school ever issues. Treat it as permanent.

§ 04Recording payments

School billing is manual by design — schools pay by bank transfer, MoMo, cash, or cheque, and we record it:

  1. Open the school → PaymentsRecord payment.
  2. Enter the date received, amount and currency, method, the reference (bank slip / MoMo ref), and the coverage period (start and end dates this payment buys).
  3. Save. The subscription extends accordingly and a receipt email goes to the school admin (resendable from the ledger; delivery status is shown per payment).

The payment ledger filters by date, method, reference, and amount, and exports to CSV.

§ 05The subscription lifecycle

Every school moves through: Trial → Active → Grace → Suspended → Canceled.

  • Grace begins automatically when the paid period lapses — the school keeps working while you chase payment.
  • Suspend (school page → Suspend) requires a written reason for the audit log. Effect: educational apps become inaccessible immediately; sign-in still works, and school admins see a banner explaining why. Reactivate reverses it the moment payment lands.
  • Entitlements (the per-app toggles on the school page) control which apps the school has, independent of payment state — flip them when a school adds or drops an app.

§ 06School admins & invites

From a school's page you can Add admin (name, email, optional phone — they get a welcome/init email) and Resend invite for an admin who lost theirs. Use this when a school's only admin departs — never hand over an existing person's credentials.

§ 07SMS administration

  • SMS Wallets — each school's SMS balance. When a school pays for credits, press Record top-up on their wallet with the amount and reference.
  • SMS Senders — schools request their own sender name; you Approve (after NCA registration) or Reject. Pending requests are the queue to watch; until approval, their messages go out as “SimuSim”.
  • SMS Dispatches — the per-message delivery history across all schools (status, failure reason), the page to open when investigating “the SMS never arrived”.
  • SMS Ledger — a separate page: the platform's own Arkesel credit accounting — runway, monthly margin, and a record of credit top-ups.

§ 08Family plans

Family Plans is the global catalogue self-serve families buy from — each plan has a display name, the apps it unlocks, the billing interval, the price, and an active toggle. Price changes are grandfathered: they apply only to new subscriptions; existing subscribers keep their snapshotted price. Deactivate a plan to stop new sign-ups without touching existing ones.

§ 09Adoption leads

Adoption leads collects every “bring Simusim to my child's school” request from the family app and the marketing site, grouped by school and sorted by demand — with an “existing customer” badge when the school is already on the platform. Work the statuses: New → Contacted → Converted / Dismissed. High lead counts on one school = warm sales call.

§ 10Audit log

The platform-wide, read-only activity feed — every onboarding, suspension, payment, entitlement flip, and email event, filterable by action, actor kind, target, and date, with before/after detail per row and CSV export. If a school asks “who changed this?”, the answer is here.

Up nextRelated guides

Help · answered by our team, not a bot

Can't find your answer?

Email us and a real person on the Simusim team will get back to you. School staff can also reach us through their school's usual support channel.