Activation Success

🎬 Simulate:

✅

Your account is ready!

Welcome, Somsak Vongphachanh.
Your account has been successfully activated.

Assigned role: Instructor

Your profile has been saved. You can update it anytime from your account settings.

Go to Staff Login

Screen Flow:

→ click Go to Staff Login → /login-staff/

📝 Spec notes — UC-IDP.03 / SCR-IDP.15 (fields, actions, requirements)

Identity

Screen: SCR-IDP.15 — Activation Success
Use case: UC-IDP.03 — Activate Staff Account

Brief description

Account activation success confirmation screen for staff/instructor (UC-IDP.03) — shown immediately after the system creates the account, before the user logs in via Staff Login (SCR-IDP.29 / UC-IDP.07). Used in three contexts per the screen spec: (1) Instructor (UC-IDP.03 main flow step 9) — after completing Instructor Profile (SCR-IDP.41); (2) Program Administrator (UC-IDP.03 AF 7A step 3) — after completing Staff Profile (SCR-IDP.42); (3) Super Administrator (UC-IDP.03 AF 7B step 1) — skips the profile form, shown directly after account creation. Serves three purposes: display a personalized welcome message, confirm the assigned role, and provide a CTA button to Staff Login. Read-only — no input form. Differs from SCR-IDP.04 (Learner Registration Success): no institution-pending state and no PIN setup step.

Fields

full_name "Full name (welcome message display)" — computed (User.firstname + " " + User.lastname) · always · read-only · fallback "" → display "Welcome!" generic message instead of erroring
role_label "Assigned role" — computed from UserRole → Role.name for the session user · always · read-only

Actions

go_to_staff_login "Go to Staff Login" — enabled when always · navigates to Staff Login (SCR-IDP.29) · triggers UC-IDP.03-M-9, UC-IDP.03-A-7A-3, UC-IDP.03-A-7B-1

Additional requirements

The welcome message must be personalized using User.firstname + User.lastname. If full_name is empty (fallback ""), display a generic greeting ("Welcome!") instead — an error must not occur in this case.
The "Go to Staff Login" CTA button must always navigate to Staff Login (SCR-IDP.29) — all activation paths (Instructor / Program Administrator / Super Administrator) share the same destination. Role-based dashboard redirect happens in UC-IDP.07 after a successful login.

⚠ Open issues

SCR-IDP.15's own spec (brief description + go_to_staff_login.triggers_uc_step) still references an "AF 7B — Super Administrator skips the profile form" path and step UC-IDP.03-A-7B-1, but the current uc-idp-03-activate-staff-account.yaml has no AF-7B — its only non-Instructor branch is AF-7A (Program Administrator, Super Administrator, or other staff position), which still goes through Complete Staff Profile (SCR-IDP.42). This prototype's navigable flow follows the UC YAML (two paths: Instructor via SCR-IDP.41, or any other role via SCR-IDP.42) — requirements should reconcile SCR-IDP.15 and the UC before this is design-final.