Go to Workers & Pages → Pages → Create a project.

Choose Direct Upload (not Git — you don't need a repo for this).

Project name: pss-tools

Click Create project.

On the deployment screen, drag and drop all 5 HTML files at once:

Click Deploy site. Cloudflare gives you a URL like pss-tools.pages.dev in about 30 seconds.

In the Pages project → Custom domains → Set up a custom domain.

Enter: tools.peachstateservices.com

Cloudflare auto-provisions the DNS record and SSL certificate. Takes 1–5 minutes.

Your tools are now live at clean URLs:

These tools have customer data and your API secret — you don't want them open to the internet. Cloudflare Access (free for up to 50 users) adds a one-time PIN or email-based login in front of the entire tools subdomain.

Go to Zero Trust → Access → Applications → Add an application → Self-hosted.

Domain: tools.peachstateservices.com

Policy: add Clayton's email + Alexis's email under "Include" → "Emails". Anyone else trying to access the URL gets a Cloudflare login screen — enter your email, receive a one-time PIN, done. No passwords to manage.

Navigate to tools.peachstateservices.com/pss-field-ops-dashboard.html

The Cloudflare Access prompt appears — enter your email, get the PIN, you're in. The dashboard shows a first-run config screen.

Enter:
API URL: https://drying-api.peachstateservices.com
API Secret: [your API_SECRET from Phase 1]

Click Connect. It tests the connection and takes you to the dashboard. Done — these credentials are saved in the browser and never need to be entered again on that device.

Navigate to tools.peachstateservices.com/pss-drying-docs-v3.html

Same first-run config screen — same API URL and secret. Both apps use the same pss_dash_cfg localStorage key, so if you're on the same browser you only enter it once total across all tools.

Same process on Alexis's phone. The Cloudflare Access invite: go to Zero Trust → Access → your application → edit the policy and add Alexis's email. She gets the same email/PIN flow on first access.

Open the Drying App → click + New Job:

Client: TEST JOB — DELETE
Address: 120 Emory Greene Dr, Macon GA
Date: today

Click Create. The job is saved. On Clayton's device, open the dashboard — the test job should appear in Active Jobs within seconds. That confirms the KV database, Worker API, and both apps are all wired together correctly.

Delete the test job from the dashboard before using for real.

Go to zapier.com → Create → Zap.

Trigger: Webhooks by Zapier → Catch Hook. Copy the webhook URL Zapier gives you.

Action 1: Jobber → Create Job (map: client_name → client name, addr → address, plan.cat → job type note)
Action 2: CompanyCam → Create Project (map: clientName → project name, addr → address)

Go back to Cloudflare Worker → Settings → Environment Variables → paste the webhook URL as ZAP_JOB_CREATED and ZAP_COMPANYCAM.

Test: create a job in the Drying App. Within seconds it should appear in Jobber and CompanyCam.

Same pattern: Webhooks Catch Hook → Jobber Find Job → Jobber Create Invoice.

Save URL as ZAP_JOB_COMPLETE in Worker environment variables.

This fires when you mark a job complete in the dashboard. The invoice auto-generates in Jobber — you review and send.

Webhooks Catch Hook → Google Sheets (Append Row to "PSS Drying Log — Master") + Jobber (Post Internal Note).

Create the Google Sheet first: name it PSS Drying Log — Master, add headers in row 1:
Map the Zapier fields to those columns.

Save URL as ZAP_DAILY_REPORT.

This fires when Alexis taps "Send to Zapier" on the Export tab of the Drying App after each daily monitoring visit.

On the office computer (or the PS Suites reception desk computer when that's live), open Chrome/Edge and bookmark the following in a PSS Tools bookmarks folder:
Add Cloudflare Access email for whoever uses the office computer.

When a receptionist comes on board, their day-one tool is the Intake Tool. They:

1. Answer inbound call via Jobber (or the Annie receptionist transfers a live call)
2. Open intake tool — fill out customer, loss details, safety flags
3. Click Create Job — job appears in KV + Jobber + CompanyCam simultaneously
4. Clayton/Alexis see it on their phone dashboard instantly

No training on Jobber required for basic intake. The tool handles the structure — they just fill in the blanks.

When I build you an updated version of any tool (new features, bug fixes, field guide changes):

1. Download the new HTML file
2. Go to Cloudflare Pages → pss-tools → Deployments → Create new deployment
3. Upload the new file — drag and drop
4. Click Deploy. Live in 30 seconds, same URL. No one needs to refresh anything — next page load gets the update.

That's it. No git, no CI/CD, no terminal. Just upload.

App shows "Offline" or can't connect:
→ Check drying-api.peachstateservices.com/health in browser. If 403 = auth working. If error = Worker is down → Cloudflare Workers → check logs.

Jobs not syncing between devices:
→ One device may be in offline/local mode. Open Settings in the app and re-enter API credentials. Or force refresh (pull down on mobile).

Zapier Zap not firing:
→ Check Worker environment variable for that Zap URL. Check Zapier task history for error messages.

Need to reset a device config:
→ Open browser DevTools → Application → Local Storage → delete pss_dash_cfg → reload → re-enter credentials on the first-run screen.