Customer, Dealer & Field-Team Portals: Isolation Enforced at the Database

Who this is for

Businesses that distribute leads or jobs across dealers, installers, or field crews, and currently do it through inboxes, spreadsheets, and group texts. Inquiries arrive by email, someone forwards them to whoever seems right, and follow-up lives in memory. Nobody can say with confidence who has which lead, what has happened to it, or which commissions have been paid.

The usual escalation paths are both wrong for a network this size: enterprise dealer-management software priced and built for someone else's problem, or more spreadsheets. We wrote about why in our article on dealer network lead distribution and our article on field teams and data access.

What we deliver

Isolation enforced where it cannot be bypassed. Portals are built on Supabase and Postgres, and the separation between users is implemented as row-level security in the database itself, not as a filter in the interface. A dealer cannot reach another dealer's pipeline through the app, through the API, or through any path at all. Admins see the whole network; everyone else sees exactly their own work.

Notification at the moment of assignment. The step that kills leads in a manual system is the lag between assignment and the dealer finding out. The moment a lead or job is assigned, an automation emails the assignee everything needed for first contact: name, phone, location, job details. No one phones the office to ask what is next.

Status workflows with an audit trail. Every lead moves through a defined lifecycle (new, contacted, quoted, booked, done) and every change is recorded. There is one record of the business, not two; walk-ins and phone leads are logged into the same system as web inquiries.

Commission and fulfillment tracking. Admins see the commission owed on each lead and whether it has been paid, alongside scheduled delivery and installation dates. The question "which commissions are outstanding" stops being a reconciliation project.

One-tap signed status actions from email. Status updates work straight from the inbox: cryptographically signed action buttons that mark a lead contacted, quoted, or lost in one tap, expire after a set window, and cannot be forged or replayed.

Capture that survives failure. Lead capture is dual-path. Every form submission writes to the database that feeds the portal and dispatches a conventional email. If any single service has a bad day, the other path still fires and no lead is lost.

Proof

For Sheds For Less, a resin shed distributor with dealers across Ontario, we built a dealer portal with database-enforced isolation, automated assignment notifications, and commission tracking. By opening day, 80% of pre-launch inventory had been reserved through the reservation flow, before the physical lot opened.

For Westlake Home Safety, a bathroom safety installer serving nine Southeastern Ontario municipalities, we built an installer job portal that carries every lead from first click to finished install. Installers see only the jobs assigned to them, on a phone-first view: today's and tomorrow's jobs, tap to call, tap to navigate, tap to mark the work done.

Questions owners ask