Suggested demo order
1
Public brand (5–7 min)
Home → themes → about. Orient everyone to Saving a Generation before portals.
01 — Home · start here for mixed rooms.
2
Split by audience
- Givers: public-sponsor (themes → donate).
- CSR prospects: public-csr → later csr-sponsor if accounts exist.
- Host prospects: public-host → later host-node (safeguarding first).
3
Portals login (shared)
Show /portal/login once, then log out between roles so tenant walls stay clear.
10 — Portals login · switch accounts deliberately.
4
Host room
Safeguarding → home → MoU / themes. Say explicitly: Hosts never see Need support.
5
CSR room
Home → profile → team. Say explicitly: CSR never sees Need support or ops support queue.
6
Ops room (staff only)
Inbox vs support queue as two stories. Verify a node; glance at audit. Keep family data off shared screens when possible.
7
Families session (optional, private)
Need-support alone. No donate pitch. Schedule separately from Host/CSR demos.
⚠ Room rules
- Never show Need support (
/need-supportor/portal/portal/admin/support) in Host or CSR workshops. - Clear auth between roles — log out; do not reuse tabs with the wrong JWT.
- Print quick-ref pages — last page of each manual laminates well.
- Screenshots missing? Run
npm run screenshotswith API + both Next apps up.
Quick reference — Facilitator
| Need | Action |
|---|---|
| Open hub | open /training/ → index.html |
| Refresh shots | npm run screenshots |
| Browser print · background graphics on | |
| Credentials | DEMO-USERS.md · Password123! |
| Hard rule | Need-support = families + ops only |