Workflow — Guest of Honor

Purpose

Handle applications for Guests of Honor — senior figures who will present awards — including manual entries by the team (e.g., government officials) made on their behalf.

Preconditions

• Toggle registration.goh on; event registration open.
• Applicant must not hold any other registration for the event (BR-001/BR-002).

Main flow (self-service)

1. Candidate opens /guest-of-honor.
2. Form: name, title (e.g., CIO), company, LinkedIn URL (auth optional at first), bio,

WhatsApp (required, BR-007), photo upload.

1. Submit → registration type=goh, status=submitted → "Under review" page.
2. Admin reviews (pending list) → approve → profile becomes visible on the event page;

notification sent. → or reject with reason.

Manual entry flow (staff on behalf) — incl. government guests

1. Staff → dashboard → Add on behalf → choose Guest of Honor.
2. Same form, plus internal note; staff account recorded in entered_by_user_id.
3. Admin approval as above. The GoH later activates their dashboard via WhatsApp/LinkedIn link (v0.4.0 simple claim flow).

Alternate / error flows

• A1 Already award applicant (or vice versa) → blocked (BR-002).
• A2 Duplicate GoH entry by staff after self-application → merge prompt: staff edits the existing pending record instead.
• A3 Approval withdrawn later by admin → profile unpublished; applicant notified.

Rules applied

BR-001, BR-002, BR-007 (+ BR-009: no public listing before approval).

Data touched

Sequence

sequenceDiagram
    participant G as GoH / Staff
    participant W as Website
    participant DB as MariaDB
    participant AD as Admin
    G->>W: GoH form (+photo, WhatsApp)
    W->>DB: registration (goh, submitted)
    AD->>W: review pending list
    AD->>W: approve
    W->>DB: status=approved
    W-->>G: notification (approved, profile live)