Users & roles

Name	Email	Role
Rakoto	rakoto@mhews.mg	Admin
Hery	hery@mhews.mg	Analyst
BNGRC Regional Office	contact@bngrc.mg	Viewer

Viewers can see dashboard severity/legends and disseminated outputs only; Draft/Pending Review content is never visible to this role (NFR-7).

Permitted actions

Role	Can see	Can do
Viewer	Dashboard, forecasts, risk, impact, historical events, and approved/released outputs only	Nothing state-changing. Submit feedback. Ask the assistant.
Analyst	Everything a Viewer sees, plus drafts, the alert queue, trigger evidence, and verification records	Prepare, assess, verify, draft, submit for review. Does not approve its own draft — an Analyst composes, an Admin approves or rejects (DD-142).
Admin	Everything	Everything an Analyst can do, plus configuration: hazards, thresholds, data sources, boundaries, layers, channels, distribution lists, users and the disclaimer. Approves and rejects drafts.

Every state-changing action is written to the audit log with its actor — no alert is created, approved or deleted without an attributable, audited user.

Not built — decision required (D-1)

The user-scenario document assigns work to duties — Duty Analyst, Reviewer, Release Authority, Data Manager, Threshold Maintainer, Verification — with scopes and deputies. FR-44 defines three roles only: Viewer, Analyst, Admin. Journeys J2, J3, J6 and O2 do not run as written under three roles: J2 alone needs a Reviewer who approves the alert and a separate Release Authority who accepts it for release.

Two ways out, and this is not the place to choose between them: either duties become assignable grants on top of the three roles (a duty roster with scopes and deputies — new scope, real build cost), or the journeys are rewritten to fit FR-44 as it stands. No duty roster is built on this screen until that is decided.

Open-decision register →