RPL personas

RPL personas

Audience: ux, product, qa
Status: specced
Owns: product + UX
Depends on: Lifecycle, Experience flows

Onboarding starts by choosing a persona (candidate, assessor, etc.).

Candidate

• Public signup; OTP for verify / password reset; password + Google auth.
• Profile holds personal info; NIN verification required before application submit.
• Owns the application through the lifecycle; chats with facilitator / panel on feedback or appeal.
• On unsuccessful interview: sees LMS course recommendations; application may CLOSED with GAP_TRAINING.

Assessor (QAA / IQM / EV)

• Selects assessor persona after account creation.
• Credentials vetted by platform staff before centre assignment.
• Rule: one assessor type per centre.
• EV must not be an assessor at the centre whose applications they verify.

Platform admin / staff

• Invite-only; set password on onboarding.
• Vets assessors; platform-scoped roles (middleware helpers).

Centre admin / staff

• Admin onboards centre details (name, address, payout account, etc.).
• Staff invite-only; set password on invite acceptance.
• Assign reviewers, facilitators, IQA, interview panels.

Awarding body admin / staff

• Similar invite/onboarding pattern to centre.
• Assign EV; process certification.