SL
SkillsLao Backoffice
Prototype
🎬 Simulate:

Complete Staff Profile

Fill in your details before accessing the dashboard

Personal information
Contact information
+856
Laos (+856) · enter local digits only (8–10 digits)
📝 Spec notes — UC-IDP.03 / SCR-IDP.42 (fields, actions, requirements)
Identity
  • Screen: SCR-IDP.42 — Complete Staff Profile
  • Use case: UC-IDP.03 — Activate Staff Account (alt flow AF-7A, role is not Instructor — Program Administrator, Super Administrator, or other staff position)
Brief description

First-time Staff Profile form — shown after account creation when the invitee's role is not Instructor (Program Administrator, Super Administrator, or other staff position — UC-IDP.03 AF-7A step 1–2). Collects Personal information (name — pre-filled from invitation, editable) and Contact information (email read-only bound to AuthIdentity; mobile optional). Clicking "Save & Get Started" saves StaffProfile and navigates to the Dashboard.

Fields
  • firstname "First name" — text · required · User.firstname · pre-filled from param.invitation_firstname · max 100 chars · editable
  • lastname "Last name" — text · required · User.lastname · pre-filled from param.invitation_lastname · max 100 chars · editable
  • email "Email" — text · required · StaffProfile.email · pre-filled from param.invitation_email · format:email · read-only (bound to AuthIdentity created during activation)
  • mobile "Mobile number" — phone · optional · StaffProfile.mobile · format:phone
Actions
  • save_and_continue "Save & Get Started" — enabled when required_fields_valid · triggers UC-IDP.03-A-7A-3 (save StaffProfile → navigate to Program Administrator Dashboard)
Additional requirements
  1. First name and last name are pre-filled from UserInvitation and editable to correct invitation errors. [refs: SCR-IDP.42 AR-1]
  2. Email is pre-filled from UserInvitation.email and read-only — it is bound to the AuthIdentity created during activation and cannot differ from the login email. [refs: SCR-IDP.42 AR-2]
  3. Screen must be responsive and work on all device types. [refs: NFR-08]
  4. Form must meet WCAG accessibility standards. [refs: NFR-09]