Site Navigation Guide
Step-by-step website walkthrough
Platform DocsLogin

Guide

Navigate the Website

Follow these steps in order the first time you use the platform. Each section explains what you see on screen and what to click next.

Step 1 — Open the app

  1. 1
    Go to the app URL
    Local development is usually http://localhost:3000 (or the port you use with npm run dev).
  2. 2
    Check the welcome screen
    You should see “Storm Response Platform” with buttons for documentation and login.

Step 2 — Landing page

  1. 1
    Read Documentation
    Opens /docs — full platform feature reference (routing, dispatch, admin).
  2. 2
    Site Guide (this page)
    Opens /docs/guide — step-by-step clicks through every screen.
  3. 3
    Continue to Login
    Opens the sign-in form when you are ready to work.

Step 3 — Login screen

  1. 1
    Enter email and password
    Use the account created in your database users table.
  2. 2
    Sign In
    The app stores a JWT token in your browser and loads the main workspace.
  3. 3
    New user?
    Switch to Create account, choose role (Tech, Office, Admin), then register. First-time setup often uses Office or Admin.

Main layout (after login)

Once signed in, the screen splits into three areas:

  • Left sidebar — switch tabs and toggle Xcel / Connexus data sources.
  • Top bar — current section name, refresh, and mobile menu.
  • Center panel — dashboard, map, lists, or admin tools.

Your name at the bottom opens Profile and Log out.

Dashboard

  1. 1
    Click Dashboard
    First item in the sidebar.
  2. 2
    Read the stat cards
    Totals for unvisited dots, opportunities, jobs in queue, and customers affected.
  3. 3
    Use before dispatch
    Office staff checks this at storm start to see workload shape.

Live Map

  1. 1
    Open Live Map
    Map loads centered on the Twin Cities area by default.
  2. 2
    Click any dot
    Detail panel shows address, status, customers, and actions.
  3. 3
    Investigate
    Opens the field form — pick outcome, power status, notes; submit in seconds.
  4. 4
    Marker updates
    Color and shape change based on status (e.g. square = door hanger).

Outages list

  1. 1
    Open Outages
    Badge shows how many dots are on the map.
  2. 2
    Filter by status
    Narrow to unvisited, investigating, etc.
  3. 3
    Search
    Find by street, city, or outage ID.

Opportunities

  1. 1
    Open Opportunities
    Confirmed damage with customer contact — not yet sold or dispatched.
  2. 2
    Follow up here
    Door hangers, thinking customers, verbal quotes stay out of Job Queue until sold.

Job Queue

  1. 1
    Open Job Queue
    Dispatch-ready jobs only.
  2. 2
    Change sort
    Priority, Distance, Value, or Smart.
  3. 3
    Assign
    See recommended tech, score, and reasons → confirm dispatch.
  4. 4
    Optimize Route
    Build stop order from tech GPS.
  5. 5
    Find Clusters
    Target dense hotspot areas.

Techs (office roles)

  1. 1
    Open Techs
    Visible to office, admin, and owner roles.
  2. 2
    Monitor crews
    Status, load, and last GPS position update every ~30 seconds when app is open.

Territories (office roles)

  1. 1
    Open Territories
    Manage ZIP lists or polygon zones.
  2. 2
    Affects dispatch
    Assignment scoring prefers techs matching job ZIP territory.

Admin (office roles)

  1. 1
    Open Admin
    Storm settings, integrations, simulation, exports.
  2. 2
    Set Storm Phase
    Phase 1 hunt → Phase 2 dispatch → Phase 3 cleanup.
  3. 3
    Temp-Out mode
    Prioritize temp power workflow when enabled.
  4. 4
    Guardrails
    Max jobs per tech and overtime limits for assign scoring.

Guide tab

  1. 1
    Click Guide
    Step-by-step navigation and login/database help inside the app.
  2. 2
    Open platform docs
    Use the link to /docs for full feature reference (routing, dispatch, admin).

Profile & logout

  1. 1
    Click your name
    Bottom of sidebar → Profile.
  2. 2
    Update details
    Change name, phone, or password.
  3. 3
    Log out
    Clears token and returns to public landing page.