Skip to content
Elimi Docs

CAP personas

CAP personas

Section titled “CAP personas”

Audience: ux, product, qa, backend
Status: specced
Owns: product + UX
Depends on: CAP overview, RPL lifecycle, NSQ lifecycle, RBAC matrix

Shared across RPL and NSQ. RPL-specific journey notes also live under RPL personas.

Candidate

Section titled “Candidate”
  1. Account via Orchestrator (email/password or Google) with CAP intent → CAP provisions cap_users + onboarding.
  2. Onboarding steps (personal information, …) then dashboard.
  3. Creates an application: RPL or NSQ — different flows after payment (see lifecycles).
  4. Identity verification (NIN) required before submit.
  5. Participates in feedback / revision loops, interview or assessment sign-off, appeals; may receive LMS recommendations on unsuccessful paths.
  6. Collects certificate via centre when awarding body issues it.
  7. The same OL account may later become centre staff (invite). Candidate onboarding stays completed; a separate staff onboarding (variant: staff) is created if missing. Workspace switch uses GET /me + X-CAP-PERSONA / X-CAP-CENTRE-ID.

Assessor

Section titled “Assessor”

Types / qualifications: QAA, IQM, IV, EV — credentials determine which centre/awarding-body requests they can apply for.

  1. Auth + onboarding (personal info, qualifications, assessor number, …).
  2. Platform admin/staff approve or reject the account.
  3. Identity verification on login / as onboarding gate.
  4. Typical work: apply to posted requests (facilitator, interview panel, IV); serve as IV at a centre; serve as EV for an awarding body; sit on interview panels.
  5. Conflict rule: an assessor cannot EV a centre where they already hold a role.

Centre admin / staff

Section titled “Centre admin / staff”

Person who registers the centre becomes super_admin. Other roles: regular_admin (everything except view/update financial details), regular staff. A person may be staff at more than one centre; role is per membership. Staff onboarding is once per person.

Before accepting candidates, appearing to candidates, or adding staff, platform admin must approve the centre.

Centre responsibilities include:

  • Assign facilitators to applications
  • Receive application payments; wallet balance; withdraw after a configured time frame
  • Schedule interviews; curate panels (3 + lead)
  • Forward IV-passed applications to the awarding body for EV
  • Issue / hand over certificates sent by the awarding body

Awarding body admin / staff

Section titled “Awarding body admin / staff”

Responsible for external verification and certification. Access assessor profiles to assign EVs (with centre conflict rule). No self-serve onboarding — platform admin adds details and sends an invite link to the provided email.

Platform admin / staff

Section titled “Platform admin / staff”

Manage and service the platform: create / approve / reject / suspend centres (and invite centre SUPER_ADMIN); approve / reject / suspend assessors; view platform revenue and payment history; manage sectors, trades, units, NOS documents; revenue config; organization/config entities; invite awarding-body users.

See also

Section titled “See also”