EnviroTech Group Back to sign in
Product Architecture

How the portal works

A guided tour of the core flows, data model, and compliance rules engine that power the EnviroTech Group Client Document Portal.

System overview

Clients
Property owners
Portal
React + secure API
Records
Firestore + Storage
Admin Console
EnviroTech ops
Rules Engine
Compliance logic
Reports
Signed PDFs

Onboarding flow

  1. 1Admin enters new client email
  2. 2System generates secure invite link
  3. 3Client sets password & verifies email
  4. 4Properties and units provisioned
  5. 5Portal access granted with scoped role

Inspection flow

  1. 1Inspector completes on-site XRF scan
  2. 2Report PDF uploaded via admin console
  3. 3Rules engine classifies unit status
  4. 4Client notified by email
  5. 5Documents visible in client portal

Compliance rules engine

Every uploaded report is evaluated against NYC Local Law 1 and HUD lead-safe housing standards. The engine produces a unit-level status badge based on the following decision tree:

Lead-safe
XRF readings below 1.0 mg/cm² on all friction & impact surfaces AND no peeling paint detected.
Lead on friction
One or more friction surfaces ≥ 1.0 mg/cm². Requires remediation plan.
Pending
No inspection on file OR inspection older than 36 months.
Role-based access
Clients see only their own properties. Admins have full scope.
Strict isolation
Per-client document tenancy enforced at the data layer.
Audit trail
Every upload, status change, and access logged immutably.

Data model

clients
  • • id
  • • name
  • • email
  • • company
  • • status
properties
  • • id
  • • clientId
  • • address
  • • unitCount
units
  • • id
  • • propertyId
  • • unitNumber
  • • status
reports
  • • id
  • • unitId
  • • type
  • • uploaded