Admin Reference
Sites Route Reference
Understand the site register, site dialogs, import entry points, and the way site-level rules affect scheduler and field workflows.
Before you start
- You are maintaining the estate register or need site-scoped context before planning or reporting work.
Expected outcome
You can use the site desk as the owning surface for site identity, contacts, notes, and source-of-truth visibility.
What this route is for
Sites owns the site register, including address data, building notes, access context, contacts, source-of-truth visibility, and the site identity used by planning and reporting desks.
Visibility and capability notes
| Item | Details |
|---|---|
| Route id | sites |
| Visibility | Customer-facing core route. |
| Capability notes | The route itself is broadly available, but import actions still depend on connected-system availability. |
| Direct inbound | Shell nav, map popups, CRM site links, scheduler warning links, activity links, and global search. |
Main regions, dialogs, and controls
| Surface | What it does |
|---|---|
| Site list | Searchable, paginated site register. |
| Source and scheduler context | Shows where the site came from and highlights scheduling-relevant rules. |
| Site mutation dialog | Create or edit the site without leaving the route. |
| Page history action | Opens site history context for review. |
| Import action | Launches staged import for systems and assets or site-related source data. |
Key actions
- Create a new site.
- Edit site identity, notes, address, contacts, and operational context.
- Open page history.
- Launch staged imports for
systems-assets. - Open the linked customer account when a CRM account is attached.
Filters and URL state
| Param | What it controls |
|---|---|
q | Free-text search |
source | Source filter such as deucalion or crm |
page | Pagination |
siteId | Selected site detail context |
create | Opens create mode |
- Search is debounced.
- The route is list-first and dialog-driven rather than tab-driven.
Outputs and side effects
- Creates or updates the site record that downstream inspections, work orders, reports, and field briefings use.
- Launches import workflows instead of doing bulk ingestion locally.
- Changes site data immediately affect how map markers, scheduler warnings, and customer-linked estate views read elsewhere.
Inbound links
- Shell
Sitesnavigation. #/mappopup actions.#/crm?tab=accounts&accountId=...- Scheduler warning or detail context.
- Activity Feed resource links.
Outbound links
#/crm?tab=accounts&accountId=...#/connected-systems?section=imports&dataset=systems-assets- Page history notification routes when history context is opened
Indirect handoffs
- Site completeness determines whether planners, engineers, and customer-facing outputs have enough context later.
- Source-of-truth notes help the office understand whether edits should happen here or in an upstream connected system.
- Site data shapes map plotting, inspection creation, work-order creation, and report scoping.
Troubleshooting
| Symptom | What to check |
|---|---|
| A site exists in CRM but not in Sites | Check whether the staged import has actually completed and whether the current source filter is hiding it. |
| A site opens but scheduler context looks wrong | Re-check site notes, access context, and scheduler-relevant fields in the site record itself. |
| The account link is missing | Confirm the site is linked to a CRM account. |
| Bulk data feels slow to maintain by hand | Use the staged import route instead of trying to recreate a full register one record at a time. |
Customers Route Reference
Understand the CRM workspace for accounts, opportunities, tasks, linked sites, finance context, and downstream commercial handoffs.
Map Route Reference
Understand the site map’s filters, popup actions, and spatial handoffs into sites, scheduler, inspections, work orders, and defects.