AISF Admin flow: from secure operations access to ecosystem oversight
No real IAM in this build — the story is the same: officers verify registrations, matches, workflows, and outcomes in one place.
Complete journey — AISF programme officer
Registration → simulated portal access → dashboard → matching → actions. Use the buttons below to jump to the real screens in this prototype.
- 1
Provisioning (narrative)
In production, AISF programme officers receive secure admin accounts. This prototype skips real IAM — go straight to the operations dashboard.
- Tell the committee: “Here we assume the officer is already authenticated.”
- 2
Observe ecosystem activity
Registrations, matches, workflow depth, and engagement tiles show whether the network is connecting — not only counting forms.
- 3
Reporting & audit
Exports and drill-downs would attach to policy workflows; here, localStorage proves the data model for committee review.
1
Officer enters operations view
- Actor action
- AISF programme staff open the admin dashboard after secure sign-in (simulated here).
- System action
- Dashboard aggregates actors, matches, workflow events, and notification queues from browser state.
- Outcome
- Leadership sees throughput, not only registration volume.
2
Verify ecosystem connectivity
- Actor action
- Team reviews actor directory, match table, and grouped workflow log.
- System action
- Each row ties back to structured profiles and explainable recommendations.
- Outcome
- Committee can audit who was matched and why.
3
Steer programmes with evidence
- Actor action
- Officers use KPI tiles and charts to prioritize schemes and convenings.
- System action
- Progress flags from the guided demo show how far the ecosystem moved in-session.
- Outcome
- Policy moves from anecdotes to dashboard-led management.
Recent workflow events
No events yet. Run the guided demo or complete a registration.