Organization-aware auth
Protected contractor routes use authenticated sessions, active organization context, module access checks, and role-aware boundaries.
Tenant boundaries and customer trust come first.
FloorConnector’s public trust story should be accurate: authenticated contractor access, organization-aware permissions, scoped portal grants, protected routes, and server-side validation are the current posture.
Built for epoxy, polishing, coatings, and specialty surface contractors.
Operating chain
From inquiry to payment
1Lead
2Customer
3Project
4Assessment
5Estimate
6Contract
7Change order
8Job
9Invoice
10Payment
No public page should expose protected app data.
No public page should promise autonomous AI or provider execution.
Security claims stay tied to implemented behavior, not future roadmap language.
Scoped portal visibility
Customer portal surfaces depend on portal grants and project access rather than broad public visibility.
Provider caution
Live sends, provider execution, payments, DNS, migrations, and production changes remain approval-gated.
Trust boundary
The public story should be impressive because it is accurate.
FloorConnector earns confidence by showing separation between public routes, protected app work, customer portal access, and owner-gated provider actions.
1
Public pages do not expose protected tenant data.
2
Customer portal visibility depends on identity, grants, and project-scoped access.
3
DNS, deploys, provider execution, payments, and live sends remain explicit owner-gated steps.
Public intake
Estimator review
Project handoff
Public pages should create confidence, then route work to the right protected place.
Marketing, contractor websites, protected contractor operations, and customer portal access are separate surfaces over one product foundation. That keeps public conversion from becoming duplicate operational truth.
Public quote and early-access capture stay server-validated.
Protected app and customer portal auth remain separate from marketing routes.
Contractor customer sites keep their own brand, colors, services, and customer-facing copy.
No public copy promises live provider execution, autonomous decisions, fake pricing, or unsupported customer claims.