1. Before you start
Part D is for people who watch the programme. Most pages here show information. A few let you record data, acknowledge a warning, or raise an escalation.
Example people
These people are fictional. They show how a role is used in practice.
| Person | Role in this example | What they do in Part D |
|---|---|---|
| Ngozi Eze | Monitoring Analyst | Records climate readings and prices, and creates risk and performance records |
| Ibrahim Sule | Programme Administrator | Resolves early warnings, creates reports, handles escalations |
| Aminu Danjuma | Executive / Donor Viewer | Reads the executive dashboard. He cannot change anything. |
| Kemi Adebayo | Investor Viewer | Reads her own organisation's portfolio and the schemes |
Role names
The role names below are used in plain English in this manual. Your screen may use slightly different wording.
| Code | Role name in this manual |
|---|---|
| PSA | Platform Super Administrator |
| CSA | Client System Administrator |
| PA | Programme Administrator |
| SCA | State Coordinator |
| IA | Institution Administrator |
| FEO | Finance Entry Officer |
| FA | Finance Approver |
| MA | Monitoring Analyst |
| AUD | Auditor / Compliance |
| EXEC | Executive / Donor Viewer |
| INV | Investor Viewer |
| SUP | Support |
Data scope
You only see records inside your data scope. A State Coordinator sees one state. An Institution Administrator sees one institution. Notifications follow the same rule. If a record is missing from your screen, check your scope with your administrator before you assume it does not exist.
Two-step verification
Some actions need recent two-step verification (MFA). Generating a report always needs it. If DFFMS asks you to set up MFA, use Security centre or Set up my authenticator first.