Vexal Intake overview
Intake collects structured leads with secure uploads and gives authorized recipients a front-facing Lead Workspace—without WordPress admin access.
Naming: Vexal Intake is not Portfolio Project Workspace intake and not Media NADMP_Intake_Upload. Those are different features.
Client surfaces
- Public / embedded intake forms (profile-driven wizard)
- Account portal:
/vexal-intake/account/ - Lead inbox:
/vexal-intake/leads/(Active / Archived / All) - Add Lead:
/vexal-intake/leads/add/ - Lead detail Workspace (CRM status, notes, timeline; status locked while archived)
Lead lifecycle (1.0.029–1.0.032)
- Clients Archive, Restore, and Mark as Spam (soft archive)—never permanent delete
- Operators permanently delete only from wp-admin (email + capability gated)
- Hub totals keep archived leads in historical counts; workflow counts exclude them
- Action buttons show busy loaders during POST redirects
Full detail: Lead Workspace.
Lead authorization
Access is based on notification recipients, invite tokens, and associated owner email—not a free-for-all subscriber login. Clients stay out of wp-admin.
Hub integration
Intake exposes Module Manifest + Workspace adapters for Hub machine pulls (Leads card summaries), including additive active_leads / archived_leads. Human login on Hub and Intake remain separate WordPress sessions on their respective installs.
Experience Framework
Intake is the reference Authentication Experience implementation for the platform. Hub mirrors the pattern with Hub-owned classes—no WI_* copies.