# STAR4Hire Core v1.7.0 — Participant Success Lite

## Before updating
1. Backup WordPress database and plugin folder.
2. Update in staging first.
3. Keep the current theme `Global Career Pulse v1.3.3` active; this release does not require a theme replacement.
4. Existing GHL / Opportunity / Manatal flow is unchanged.

## What the upgrade creates
WordPress will add four tables through the existing Core DB upgrade mechanism:
- `wp_s4h_program_enrollments`
- `wp_s4h_success_actions`
- `wp_s4h_participant_documents`
- `wp_s4h_service_entitlements`

It also creates the page:
- `/success-workspace/` → `[s4h_success_workspace]`

And the role:
- `STAR4Hire Participant Success`

## First pilot: TND
### 1. Create a staff user
WordPress → Users → Add/Edit User → Role: **STAR4Hire Participant Success**.

### 2. Activate one participant
WordPress → STAR4Hire → Participant Success → **Activate Participant / Program Enrollment**.

Fill:
- Talent ID
- Program = TND
- Primary Success Manager
- Start/Target date
- `Create linked JourneyOS journey` = ON for a new journey
- `Add editable starter documents/services` = ON for the pilot

> Starter items are only an operational starting point. Edit them to match the participant's actual signed agreement.

### 3. Add accountability actions
Open the enrollment and add Action Cards.
Examples:
- Explain DreamLeap Beyond pathway → Waiting on STAR4Hire
- Confirm internship interest → Waiting on Participant
- Employer shortlist → Waiting on STAR4Hire
- Sponsor feedback → Waiting on External Partner

Use **+ Add Custom Action** whenever an extra process is needed. Do not create a new Journey stage for one-off exceptions.

### 4. Documents — Phase 1
The participant keeps/uploads the file in Google Drive and pastes the link.
Core stores only:
- document requirement
- Google Drive URL
- status
- due date
- verifier / verification timestamp
- revision note

Participant upload flow:
Google Drive → share with the authorized STAR4Hire account/group → paste Drive link in secure Track My Journey.

No document binary is uploaded to WordPress in v1.7.0.

### 5. Team daily view
Staff login → `/success-workspace/`

They see:
- Overdue
- Due Today
- Next / Unscheduled

Click **Open participant** to see one screen with:
- current Journey stage
- Primary Owner
- Waiting on Participant / STAR4Hire / External
- open actions
- documents
- services/classes

### 6. Participant view
Use the secure participant Journey link generated by JourneyOS.
The participant sees only:
- Where am I?
- What do I need to do?
- What is STAR4Hire working on?
- Documents
- Included services/classes

A participant can submit a Google Drive link or mark a participant-owned action complete only from the secure Track My Journey link.

### 7. Parent view
Parent Journey remains read-only and intentionally limited. Only items explicitly marked for Parent visibility are shown.

## UAT checklist
- [ ] Existing Talent IDs remain unchanged.
- [ ] Existing GHL bridge still passes Test Connection.
- [ ] Existing `/opportunities/` still works.
- [ ] Existing JourneyOS pages still render.
- [ ] Create one dummy/test enrollment.
- [ ] Linked Journey is created when selected.
- [ ] Custom STAR4Hire action appears in My Work Today.
- [ ] Participant action appears in Track My Journey.
- [ ] Participant can mark participant-owned action complete with secure token.
- [ ] Add document requirement.
- [ ] Non-Google URL is rejected in participant document submission.
- [ ] Google Drive link saves as Submitted.
- [ ] Operation can mark Verified / Revision Required.
- [ ] Service/class progress renders on participant view.
- [ ] Parent view does not expose internal notes or hidden items.
- [ ] Management metrics update by responsibility.

## Phase 1 scope deliberately NOT included
- Google Drive API / automatic Shared Drive folder creation
- Full LMS
- Attendance session-by-session database
- Payment installment engine
- Auto-enrollment from GHL payment webhook
- Specialist case routing engine
- Participant mobile app

Those can be added after TND validates the daily operational flow.