Who's on this job

Assign team members to a project; assigned people always get its start, stage-complete and completion notifications.

What it is

A per-project assignee picker listing org members, with add and remove. Assignments drive project-level notification routing regardless of org-level role preferences.

Also called: assign people to a project · project manager on this build · who gets notified about this job

See it
Who's on this job
Apr
May
Jun
Jul
Sutter Kline — Hobby Shop
Framing
Gideon Alt — Hobby Shop
Concrete
Gideon Alt — Riding Arena
Trim
Delia Yoder — Hobby Shop
Framing
Ivy Brubaker — 30×40 Garage
Concrete
Framing crewConcrete crewTrim crew
Assignee row with member avatars and an add-person picker in the project modal — ProjectAssigneesPanel.tsx. Sample data — no customer information appears here.
How it works
  1. 1Reads org members and existing project_assignments for the project
  2. 2Adds and removes write through the database proxy; org scoping is enforced server-side
  3. 3The stage automation engine resolves 'assignees' as a recipient class
Why we built it

Company-wide notification settings can say 'tell the project managers about every job'. They cannot say 'tell the site lead about this one build', and the person a builder actually wants woken up is almost always specific to the job. People assigned to a job always hear when it starts, when a stage completes and when it finishes, whatever the company-level preferences say.

The problem
  • Per-job responsibility being invisible
  • Notification routing that can only be set globally
Sound familiar?
What you get
The people on a job always hear about it
Responsibility is recorded on the job

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 →