Admin Route Interaction Matrix
Look up how each customer-facing admin route links to other routes, which entities it owns, and what downstream work it triggers.
Before you start
- You need to understand how the office-side pages connect to each other rather than how to complete one workflow.
Expected outcome
Teams can trace where each admin route sends users next and which shared records it changes.
How to read this matrix
| Column | Meaning |
|---|---|
| Direct inbound | Pages that can open or hand off directly into this route. |
| Direct outbound | Pages this route can open directly through buttons, tabs, map popups, or route-aware actions. |
| Shared entities | Records this page creates, edits, reviews, or depends on. |
| Indirect handoffs | Downstream surfaces affected even when no direct route jump exists. |
Core and operations routes
| Route | Direct inbound | Direct outbound | Shared entities | Indirect handoffs |
|---|---|---|---|---|
| Dashboard | Default landing route and office reset point. | Integrations, Scheduling, Reports, Inspections, Assets, Defects, Work Orders, Quotes, Map, and admin-only health/users surfaces. | Workload summaries, integration status, sites, inspections, defects, quotes, work orders. | Changes what the office triages first; pushes teams into the live desk that owns the record. |
| Customers | Finance can reopen a customer billing profile; sites, quotes, work orders, routines, and handover packages depend on customer context. | Organization service policies, Quotes, Report Writer, routine generation into Scheduler, AI Assistant via CRM workspace actions. | Customer accounts, opportunities, tasks, service-policy snapshots, linked sites, service contracts, routines, quote candidates. | Feeds quotes, finance, work orders, routine generation, and report-writing context without forcing duplicate customer data entry. |
| Client Handover | Data Quality and customer/site handover workflows can open a package. | Customer handover package access and source records by id. | Handover packages, package items, grants, and package events. | Publishes or revokes customer-safe access to reports, inspections, quotes, and work orders. |
| Sites | Scheduler, map popups, imports, and list flows all converge on the site record. | Site-scoped inspections, report scope, staged imports, and system or asset management flows. | Sites, site contacts, building metadata, ownership context, linked systems and assets. | Site data drives engineer briefings, report branding scope, certificate context, and map visibility. |
| Map | Dashboard or sidebar entry when spatial triage matters. | Sites, Scheduling, Inspections, Work Orders, Defects from map popups and spatial drill-in. | Site geography, workload density, defect and work-order location overlays. | Helps route office users into the right record without changing the underlying record itself. |
| Scheduling | Dashboard, map, inspections, work-order desks, and routine generation all push work back into scheduler planning. | Site detail routes and job detail routes through detailHref, PPM Forecast drill-downs, plus batch dialogs and deploy flows. | Planned jobs, assignments, booking status, buckets, engineer visibility, deployment state, customer notifications, backlog, recurring imports, day runs. | The most important office-to-field handoff surface; scheduler state changes what engineers see as live work and what customers are told about appointments. |
| PPM Forecast | Dashboard and management workflows open future capacity review. | Scheduling date-range, service-line, postcode-area, site, and unassigned slices. | Future inspections, work orders, planner tasks, bucketed demand, engineer capacity. | Changes planning decisions, not live records; exposes future pressure before it hits daily dispatch. |
| Data Quality | Dashboard and management workflows open hygiene review. | Sites, Assets, Customers, Defects, Report Writer, Client Handover, and CRM-linked records through sample hrefs. | Data-quality rule samples and reviewed keys, plus source records in owning desks. | Pushes admins into the owner desk for remediation rather than becoming an edit surface. |
| Workforce Productivity | Dashboard and management workflows open workforce review. | Scheduling completed-job slices and Defects QA follow-up. | Aggregate engineer productivity, attendance, acknowledgement, late/rebooked, and QA signals. | Changes management focus, not live records; source fixes still happen in Scheduling, Inspections, Work Orders, and Defects. |
| Inspections | Dashboard, map, scheduler detail links, and site/report follow-up all converge here. | Scheduling for plan changes. | Inspection records, result state, planned dates, completion metadata, certificate-ready visits. | Completed inspections feed certificates, defects, reports, quotes, and activity history. |
| Defects | Dashboard and map can route office users straight into defect review. | Mostly in-place triage rather than direct route jumps. | Defect backlog, severity, status, linked assets, remediation state. | Drives work-order creation, inspection review, reporting, and engineer follow-up. |
| Quotes | Dashboard, CRM opportunity actions, certificate follow-up, and mobile quote create handoffs feed this desk. | Work Orders after acceptance and Finance through receivable context. | Quotes, commercial status, linked inspections, linked customers, line items, approval grants, approval responses, approval events. | Accepted quotes become work-order input and receivables candidates; approval events explain why quote status changed. |
| Work Orders | Dashboard, map, search flows, quote acceptance, and contractor submissions feed this queue. | Scheduling for assignment and date planning; Contractors for staged external submissions. | Remedial jobs, linked quotes, linked defects, linked customers, assignee state, contractor job-pack source context. | Deployed work orders surface in mobile work-order views, contractor packs, and receivables later. |
| Organization | CRM and commercial setup send admins here for service policies and team setup. | Mostly in-place section changes rather than cross-route navigation. | Organization profile, members, invitations, seat/billing state, service policies, feature access. | Governs workspace visibility, field-work eligibility, and output branding across the product. |
| Finance | Customer/CRM billing context, quotes, work orders, and dashboard commercial finance attention can route here. | Quotes, Work Orders, CRM account finance, and accounting export consumers. | Receivables, billing candidates, invoice drafts, payments, void/write-off actions, workspace billing. | Updates account health that later changes CRM follow-up, work-order release decisions, invoicing, and office reporting. |
| Assets | Site and system administration flows converge on asset review and export. | Mostly modal/detail operations inside the route. | Physical assets, asset type, status, owner system/site, import/export state. | Asset changes alter inspection checklists, field selection, history, and reporting output. |
| Systems | Site and asset setup rely on this desk for the installation layer. | Mostly in-place system management. | Systems, system type, ownership, linked assets. | System changes alter scheduler context, engineer discovery binding, and report grouping. |
| Contractors | Contractor submissions and external job-pack workflows feed this queue. | Work Orders through approved merge and review context. | Contractor submissions, contractor access grants, contractor events, work-order payload updates. | External contractor updates become official only after admin approval and merge. |
| Insights | Dashboard or direct entry for analytics review. | No major direct route jumps; it is a read-heavy analysis surface. | Aggregate inspection, defect, work-order, and usage trends. | Changes office decisions, not live records. |
| Reports | Dashboard and completion review send admins here to generate outputs. | Report Writer and platform-only report intelligence. | Site packs, inspection-scoped exports, compliance PDFs, defects PDFs, certificate bundles, CSV exports. | Produces customer-facing artifacts that depend on sites, inspections, defects, and certificates remaining clean. |
| Report Writer | Reports and CRM actions can open the review queue. | Mostly route-local review actions. | Drafted report content, review state, blockers, confidence signals. | Approved draft content changes what gets exported from the reports desk. |
| Document Templates | Report and template-administration workflows converge here when the output structure itself needs work. | Mostly route-local tabs and version/history transitions. | Template lifecycle, versions, branding, render history. | Template changes alter later report and certificate output without changing source records. |
| AI Assistant | CRM task/opportunity actions and route-scoped prompts can open it. | A platform-only AI operations workspace exists but is out of scope for customer docs. | Route-grounded AI conversations, current page context, follow-up prompts. | Helps admins pivot back into the owning desk with more context but does not replace record editing surfaces. |
Connected systems and collaboration routes
| Route | Direct inbound | Direct outbound | Shared entities | Indirect handoffs |
|---|---|---|---|---|
| Connected Systems | Main hub for connections, imports, API keys, and webhooks. | Embedded sections for Integrations, Imports, API Keys, and Webhooks. | Connection records, staged import runs, API credentials, webhook endpoints. | Centralizes external-system setup that later affects scheduler data, imports, and automation. |
| Integrations | Connected Systems Connections section and dashboard integration cards. | Mostly in-place dialogs and sync-log inspection. | External connections, sync status, direction, entity mappings, run history. | Changes what source-of-truth data can flow into sites, assets, customers, and work orders. |
| API Keys | Connected Systems API Keys section. | Mostly in-place create/reveal/revoke flows. | Scoped API credentials for automation and external clients. | External automation can later create or query customer-facing records. |
| Webhooks | Connected Systems Webhooks section. | Mostly in-place endpoint management. | Webhook destinations, subscribed events, shared secret material. | Downstream receivers can react to inspections, quotes, work orders, and other record changes. |
| Activity Feed | Collaboration workflow guides and top-bar triage context. | Linked resources send the admin back into the owning live desk. | Structured event history for sites, inspections, defects, quotes, work orders, and comments. | Does not own records, but it is the fastest way to discover that another desk changed one. |
Routes with no meaningful direct cross-route navigation
Some routes still matter to the wider product even when they do not push users into many other pages directly:
Insightsis intentionally read-heavy. Its main interaction is decision support, not route hopping.Report Writerkeeps review decisions local to the queue.Document Templatesmostly changes template versions and render behavior inside its own workspace.Activity Feedis a context surface first; it hands users back to the owning resource rather than becoming the source of truth itself.
Use the Entity Lifecycle Atlas when the better question is “where does this record type live?” rather than “which route links to which route?”.
Primary table hubs behind the main admin desks
| Admin route | Primary tables |
|---|---|
| Customers | crm_accounts, crm_contacts, crm_opportunities, crm_tasks, crm_activities, crm_documents, crm_sla_templates |
| Client Handover | customer_handover_packages, customer_handover_package_items, customer_handover_grants, customer_handover_events |
| Sites / Systems / Assets | sites, site_industries, systems, assets, asset_inspection_status |
| Scheduling / PPM Forecast | scheduler_tasks, scheduler_buckets, scheduler_deployment_batches, scheduler_deployment_items, scheduler_notification_deliveries, scheduler_customer_notifications, scheduler_changes, plus booking, bucket, visibility, routine, and deployment fields on inspections and work_orders |
| Inspections | inspections, inspection_items, inspection_visit_notes, flow_rate_measurements, defects |
| Quotes / Work Orders / Finance | quotes, quote_line_items, quote_approval_grants, quote_approval_responses, quote_approval_events, quote_approval_attachments, work_orders, work_order_items, work_order_assignments, crm_invoices, crm_invoice_payments |
| Routine Contracts | service_contracts, routines, plus routine fields on inspections and scheduler_tasks |
| Contractors | contractors, contractor_access_grants, contractor_access_events, contractor_submissions |
| Reports / Report Writer / Document Templates | generated_reports, document_templates, document_template_versions, organization_document_template_assignments, organization_pdf_branding, document_render_history |
| Connected Systems | integration_connections, integration_entity_maps, integration_sync_log, integration_import_runs, integration_import_rows, api_keys, webhooks, webhook_deliveries |
| Activity Feed | page_history_events, page_comments, mention_notifications, with older audit-comment data also visible in some flows |
| AI Assistant | ai_conversations, ai_messages, ai_pending_confirmations, ai_usage_log |
Database Table Atlas
Map the customer-facing product atlas back to the main Supabase-backed Postgres tables so teams can see which persisted records power each workflow.
Engineer Screen Interaction Matrix
Look up how each customer-facing mobile screen opens, what it can launch next, and which records or outputs it affects.