A capability-gated console listing every crew in a tenant with its lead, members, pending and active acceptance counts, and a problems list flagging crews that need attention — then four repair actions.
Also called: crew has no lead · orphaned crew · move contracts to another crew · fix a broken crew
- 1GET returns crews with members resolved from Clerk publicMetadata.crewId plus acceptance counts and problem flags.
- 2set_lead updates crews.lead_user_id, writes the new lead's Clerk metadata (role, crew, org) and upserts crew_members_sync so they appear in TeamView.
- 3reassign_acceptances bulk-moves pending and active assignments between two crews in the same tenant.
- 4rename changes the display name only; the id stays.
- 5delete is refused with a 409 and the blocking counts unless the crew has no members, no acceptances and no signatures.
A crew holding six jobs waiting on a signature, with no members and no lead, is work that nobody in the company can sign off — and the builder's own screens cannot get him out of it, because every fix needs a lead who is not there. Support repairs it from outside: either install a lead so the waiting work can be signed, or move the work to a crew that already has one. It exists because orphaned crews holding live jobs is a recurring class of problem rather than a one-off.
- Work stranded on a crew with no leader or members.
- Tenant admins unable to repair their own data.
- Destructive deletes that would orphan signed records.
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 →