Admin overview

The admin role is for Keybaki operators — the people who keep the platform healthy. Admins see everything (no role scoping) and have surfaces no other role has: account moderation, school verification, broadcasts, integrations status, money reconciliation.

What you can do

• Users — search, suspend, change role, change scope, audit, merge.
• Schools — registry CRUD + verification queue.
• Class streams — manage class structure for partner schools.
• Audiences & broadcasts — segment users + send announcements.
• Idle slides — kiosk content editor (DB-backed; auth pages consume it).
• Bulk invites — operator-led import of users.
• Trust & safety — content flag review queue.
• Money — M-Pesa reconciliation, token bundle ops.
• Integrations — env-var-driven service status, dispatcher health.
• Platform metrics — usage, sign-ups, retention.
• Operations — data exports, system actions, audit trail.

Default surfaces by frequency of use

Most-used (daily): Users list, Verification queue, Trust & safety. Weekly: Broadcasts, Bulk invites, Integrations status. Occasional: Audiences, Idle slides, Money recon, Operations, Account merges.

What admins don't do

• See child PINs (only hashes; no decoder).
• Decrypt private notes attached to plans.

Common starting points

• A user is complaining their account is locked → Users list → find them → check status. See Suspending and restoring users.
• A teacher claim came in → Schools → Verification queue.
• Need to send a message to all parents in Nairobi → Audiences → build segment → Broadcasts.
• A library item is being flagged a lot → Trust & safety → flag queue.

Common issues

• Some buttons say "Requires super-admin". Regular admins can't suspend other admins. Super-admin status is granted out-of-band by an existing super-admin.
• Admin chrome feels heavy. The side rail surfaces many admin entries by design. Use the search shortcut (Ctrl/Cmd+K) to jump.