Admin Sitemap
This is the locked V1 admin sitemap for IED.
Use this as the source of truth for:
- admin routes
- primary admin navigation
- which operational areas deserve top-level pages
- what belongs inside detail pages instead of becoming its own route
V1 Route Map
Primary Admin Pages
/Dashboard/leadsLeads list/leads/[leadId]Lead detail/installersInstallers list/installers/[installerId]Installer detail/regionsRegions list/regions/[regionId]Region detail/follow-upsFollow-ups list/follow-ups/[followUpId]Follow-up detail/contact-inquiriesContact inquiries list/contact-inquiries/[inquiryId]Contact inquiry detail/billingBilling operations/analyticsReporting/settingsSettings/learnLearn hub (internal operator documentation)/learn/[slug]Learn document page
Primary Admin Navigation
V1 admin nav:
- Dashboard
- Leads
- Installers
- Regions
- Follow-Ups
- Contact Inquiries
- Billing
- Analytics
- Settings
Secondary account-menu nav:
- Learn
Rules:
Dashboardis the top-level name for/Settingsstays a single top-level route in V1Analyticsstays a real top-level route even if the first version is intentionally lightweight
Route Intent
Dashboard
Purpose:
- high-level operational visibility
- key counts, status summaries, and pipeline health
Leads
Purpose:
- primary operating surface for incoming work
- assessment review
- recommendation review
- routing actions
- activity history
Installers
Purpose:
- manage installer records, coverage, tiering, and operational notes
Regions
Purpose:
- manage service areas, postcode ownership, and preferred installer relationships
Follow-Ups
Purpose:
- track post-install satisfaction, issue handling, and completion
Contact Inquiries
Purpose:
- triage non-assessment inbound website contact requests
- keep a separate lane for users who do not complete the assessment flow
Billing
Purpose:
- run period billing operations for installer delivery charges
- review invoice, payment, and reconciliation workflows
Analytics
Purpose:
- view reporting and operational metrics outside the dashboard summary layer
Settings
Purpose:
- hold app-level and operational settings that do not deserve separate V1 modules
Learn
Purpose:
- provide authenticated, plain-language onboarding and operations guidance for non-technical users
- explain statuses, page responsibilities, and daily workflow expectations
V1 Exclusions
These do not belong in the V1 admin sitemap:
/system/recommendations/routing-rules/activity-log/users
Ownership Notes
- recommendation review lives inside lead detail
- routing controls live inside lead detail
- activity and history live inside the owning detail surfaces
- installer-specific operational history lives inside installer detail
- region-specific availability and assignment rules live inside region detail
Transitional Repo Note
/system is not part of the target V1 sitemap and should remain excluded from operational navigation.