The dashboard is passed into the hub as a slot rather than imported, so the tab exists exactly where the caller has a dashboard to show. Task chrome (the + New task button, the list/calendar switch, the filters) hides on the dashboard tab. Below the task list the caller can hang further sections — the callback queue and the field log both live there.
Also called: home dashboard · landing screen · what shows when I log in
- 1TaskHub takes dashboardSlot and belowTasksSlot as React nodes; with a slot present the default view is 'dashboard'.
- 2AppShell mounts one TaskHub for the 'fieldlog' view carrying DashboardView as the slot; the old standalone dashboard view renders null so its queries are not doubled.
- 3The agency panel mounts the same component with no dashboard slot, so its tabs and default are unchanged.
Quoted in the file: “I want to add a third one, Dashboard. So it would be Dashboard, and that's what it defaulted to when you clicked Home, but then you could click My tasks and Assigned to others.” The slot (rather than an import) exists because 'a tenant dashboard rendered inside the agency's own Home would be somebody else's data on the wrong screen'. Mounting a second DashboardView would also have doubled every query it makes, since views stay mounted.
- Two separate landing screens
- A duplicated dashboard doubling its own queries
See it on your own jobs
Twenty minutes, your numbers, no slide deck. We’ll build one of your real buildings in front of you and send you the estimate link at the end — yours to keep either way.
or keep browsing features →