Crew-scoped dashboard

A user who cannot view all crews sees only their own crew's projects in every dashboard widget.

What it is

Permission enforcement applied to summary widgets, not just detail screens. The project list the dashboard derives from is filtered to the viewer's own crew, and a user with no crew assigned sees none rather than all.

Also called: crew only sees their jobs · dashboard permissions · hide other crews' work

See it
Crew-scoped dashboard
New lead 3
Marlin Hoover
$41k
Delia Yoder
$42k
Contacted 2
Sutter Kline
$31k
Ronan Petsch
$53k
Ivy Brubaker
$55k
Estimate 4
Ivy Brubaker
$48k
Gideon Alt
$38k
Sold 3
Marlin Hoover
$55k
Delia Yoder
$70k
Sutter Kline
$61k
The same dashboard viewed as a crew lead — Active Projects listing only that crew's jobs. DashboardView.tsx. Sample data — no customer information appears here.
How it works
  1. 1If the role permits viewing all crews, every project is used.
  2. 2Otherwise the effective crew is resolved and projects are filtered to it.
  3. 3No effective crew resolves to an empty list, failing closed.
Why we built it

The comment states the risk it closes: it 'Mirrors the GanttChart guard so the dashboard can't leak other crews' work via summary widgets.' Aggregate views are a common blind spot in permission models.

The problem
  • Summary widgets bypassed the crew scoping enforced elsewhere.
Sound familiar?
What you get
Crew members get a useful dashboard limited to their own work.
Permission rules hold on aggregate screens as well as detail ones.

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 →