MySentinel docs
Welcome. MySentinel is an NFC-badge learner movement-tracking and school-safety platform built for South African schools, running entirely on Cloudflare. A security officer scans a learner’s badge at the gate; MySentinel validates the check in or check out, records it immutably, updates a live admin dashboard and attendance in about a second, and notifies every verified guardian push-first (web push → email → WhatsApp → SMS). It speaks English, Afrikaans and isiZulu, keeps learner photos and guardian contacts encrypted at rest, and is built around POPIA from the ground up. This site is the single home for everyone who touches MySentinel — whether you are pitching it to a school group, running a demo, working a daily shift on it, or vetting it as a technical advisor.
Who each section is for
| Section | For you if you want to… | Tone |
|---|---|---|
| Sell | Pitch MySentinel to a chain owner or principal — the value story, pricing (~R10/learner/month), and an honest roadmap. | Confident, evidence-led |
| Demo | Run a live walkthrough that lands every time, on the right environment, with the right framing. | Step-by-step runbook |
| Use | Do the job — scan at the gate, run the admin workspace, take a daily roll, onboard a campus, or check on your child. | Task-oriented “you” guides |
| Due diligence | Verify the claims — architecture, tenancy, security, encryption, and exactly what is shipped versus roadmap. | Plain, no hand-waving |
Start here
New to MySentinel? Read these three first, in order.
- Pitch deck — what MySentinel is, who it is for, and why it earns trust. The honest proven-versus-roadmap line is part of the pitch, not a footnote.
- Demo runbook — the rehearsed chain-owner storyline: operator console as a wall-board → onboard a campus live → drop into one school as admin → the gate flow → the guardian portal → trust and compliance → commercial close.
- The five persona guides — one short guide per role (below). Each opens with what the role can and cannot do, then walks the everyday tasks.
The five persona guides
MySentinel has five personas. Each guide is written in second person and is scoped to exactly what that role sees.
| Role | What they do | Guide |
|---|---|---|
| Officer | Scans badges at the gate, confirms check in / check out, signs visitors in and out. Works on a phone, offline-tolerant. | Officer guide |
| Admin | Runs the full /admin school workspace — dashboard, learners, classes, attendance, emergency, safety mode, settings, staff, reports. | Admin guide |
| Class teacher | Captures the daily roll and approves pickup requests, scoped to their assigned classes only. | Class teacher guide |
| Operator | Cybertron platform staff — onboards new campuses through a durable Cloudflare Workflow and watches platform health. | Operator guide |
| Guardian | Opens the tokenised parent portal at /p/[token] — no login — to see each child’s real-time status and manage requests. | Guardian (parent portal) guide |
A quick orientation
- The gate is the hero. An officer taps a badge, picks In or Out, and chooses “arrived on their own” or “dropped off by a guardian” — guardian presence is recorded but optional. The screen confirms with an unmistakable green “CHECKED IN”, a server timestamp, and “Guardians are notified on their verified contacts.”
- The dashboard answers first. Admins land on “Today’s school status” — who is on-site, who has left, who has not tapped yet — with a go-live checklist, class roll-up, and patterns to watch.
- Onboarding is a click, not SQL. Operators fill a three-step form and watch a durable Workflow tick provisioning steps green in real time.
- Honesty is built in. Channels show Preview versus Live badges and never fake a “sent”. Colours are semantic everywhere: green = confirmed, amber = queued or at-risk, red = emergency only.
Honest status at a glance
We mark anything not yet live as Roadmap throughout these docs, because a buyer’s technical advisor will check — and the honesty is part of the sell.
| Today | Status |
|---|---|
| Officer gate flow (real NFC badge tap on Android, offline “Queued → Sent” outbox), guardian-optional release, real-time admin dashboard, deep per-school settings | Shipped, verified on UAT |
| Operator console + onboarding a new campus via a durable Workflow | Shipped, verified live (local) |
| Class-teacher scoped workspace + live pickup approvals; tokenised parent portal | Shipped, verified live (local) |
| RBAC tenant isolation, passkey step-up, channel honesty, trilingual en/af/zu, real web push | Shipped, verified live (local) |
| Group-scoped owner role — today “operator” is platform staff who sees every school on the platform, not an owner scoped to one chain | Roadmap |
Physical per-campus sharding — shard-ready in code, but only shard_0 is live (logical isolation by school_id today) | Roadmap |
| WhatsApp + SMS delivery — live and tested on UAT; each school still connects its own provider to switch them on per school (until then they demote to email) | Shipped, verified on UAT |
| Web push arriving on a real device, branded PDF / SAR rendering (Browser Rendering) | Shipped, verified on UAT |
Where to demo: UAT only. Production is currently a hollow shell with no secrets — it is not yet a live environment. The demo runbook covers this framing.
For the full, line-by-line verdict behind this table — including the live walkthrough evidence and the fix-before-demo checklist — see the Due diligence section.