A chip strip of crews above the chart, with inactive crews hidden by default and inactivity badges for crews currently on time off. For roles without canViewAllCrews the chip strip is hidden entirely and the project list is hard-filtered to their own crew regardless of filter state.
Also called: filter by crew · crew chips · crew only sees their own jobs
- 1Crew ids come from the projects plus the stored crew list; inactive crews are filtered out unless 'include inactive' is on
- 2Crew inactivity badges are memoised per crew/time-off change rather than parsing localStorage on every pan frame
- 3The projects memo applies the crew restriction before any UI filter — 'defense in depth: even if a UI control leaks through, other crews' projects stay out of the data layer'
- 4selectableCrewIds separately limits which crews a crew lead may ASSIGN to, so they cannot book time off for another team
Crew leaders and workers get their own logins, and the first version showed them the whole board. That let any subcontractor read every other sub's jobs, dates and workload — a privacy problem for the crews and a pricing problem for the builder, who does not want one sub counting how much work another one is getting. Crew accounts see only their own crew's jobs, and that is enforced on the server rather than by hiding rows on screen.
- Crew members seeing the whole company's workload
- A crew lead reassigning work or time off outside their authority
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 →