<- Support projects

Support Project · Blade

onboardingflow-laravel-proof

Laravel onboarding workflow proof with tracked invites, public submission, SharePoint document evidence, review, follow-up, roles, reporting, and audit history.

Repository readme / adapted

OnboardingFlow

SOURCEREADME.mdAdapted for portfolio readability; claims remain source-derived.

OnboardingFlow is a Laravel/MySQL proof-of-concept for a trackable onboarding workflow.

It was built as a standalone sample-data project to demonstrate how an onboarding process could move from manual emailed documents into a structured review workflow with invites, submissions, document requirements, review steps, missing-information follow-up, SharePoint-backed uploads, reporting, and activity history.

This proof is **not connected to OSHE systems** and is **not production-ready**. It is intended as a safe visual and technical proof-of-concept.

01

Project Summary

OnboardingFlow demonstrates a complete onboarding review loop:

The purpose of the proof is to make the workflow easier to review visually before any real pilot or production work is considered.

  • An admin creates an onboarding template.
  • An admin creates an invite for an applicant.
  • The applicant opens a public onboarding link.
  • The applicant submits details and uploads required documents.
  • Uploaded documents are stored through SharePoint.
  • A reviewer checks the submission, checklist, and document requirements.
  • If information is missing, the reviewer can request updates.
  • The applicant can reopen the same link and resubmit.
  • The reviewer continues review and can approve the onboarding.
  • Activity history and reports show the workflow trail.
02

Video Walkthrough

A full walkthrough video is available here:

OnboardingFlow Proof-of-Concept Walkthrough

The walkthrough demonstrates the full sample workflow, including invite tracking, public submission, SharePoint document uploads, reviewer checks, missing-information follow-up, applicant resubmission, activity history, and reporting.

03

Screenshots

Screenshots are stored in:

docs/screenshots/
04

What It Demonstrates

  • Template-based onboarding invites
  • Public applicant onboarding form
  • Submission tracking
  • Required document tracking
  • SharePoint-backed document uploads
  • Reviewer checklist
  • Missing-information detection
  • Missing-information follow-up messages
  • Applicant resubmission workflow
  • Admin / Reviewer / Read-only roles
  • Activity history / audit trail
  • Reports page
05

Tech Stack

  • Laravel
  • PHP
  • MySQL
  • Blade
  • Tailwind CSS
  • Microsoft Graph
  • Outlook email sending
  • SharePoint document storage
06

Development Tools

  • Laragon for fast local PHP/MySQL proof-of-concept development
  • Composer
  • npm / Vite
  • Cursor for AI-assisted code editing and project iteration
  • ChatGPT for planning, debugging support, documentation drafting, QA planning, demo review, and packaging
  • Git / GitHub for version control and project presentation
07

Local Development Environment

This proof-of-concept was built locally using **Laragon** to move quickly on a Windows development machine.

Laragon was used for the proof because the priority was to rapidly validate the onboarding workflow, database structure, Microsoft Graph email flow, SharePoint document uploads, reviewer process, QA checklist, screenshots, and demo packaging.

This does **not** mean Laragon would be the preferred environment for a real pilot or production project.

For a production-aligned setup, the environment should be reviewed against the organisation's existing stack, development standards, deployment process, hosting approach, and security requirements. Based on the stack previously described for the live environment, that may include Laravel/PHP, MySQL, Composer, npm, Git, React/JavaScript, Tailwind CSS, Lando, Docker, Linux hosting, and the organisation's existing hosting/security requirements.

08

Recommended Demo Path

  • Log in as admin.
  • Open the dashboard.
  • Open the invite list.
  • Open an onboarding invite.
  • Open the public applicant form.
  • Submit applicant details and upload required documents.
  • Confirm uploaded files appear in SharePoint.
  • Review uploaded documents from the admin/reviewer screen.
  • Mark the invite as Needs Info.
  • Preview or send the needs-info follow-up email.
  • Open the same public link in resubmission mode.
  • Resubmit missing information and documents.
09

Demo Users

After seeding:

admin@example.com / passwordreviewer@example.com / passwordreadonly@example.com / password
10

Admin

Admin users can:

  • Create templates
  • Create invites
  • Send invite emails
  • Review submissions
  • Update document status
  • Add notes
  • Send needs-info emails
  • Export CSV
  • View reports and activity history