Me is the first option and is never listed twice. Everyone else comes from the shared roster, with the role label appended so two people with the same first name are distinguishable. If the chosen person has no login, a line explains the task will show on the project but will not reach them directly, and points at Team to invite them.
Also called: assign to a crew member · hand off a task · give it to someone · delegate
- 1The picker reads /api/team/roster — the union of all four staff stores — which any signed-in user may read.
- 2Inactive people are filtered out; the current user is filtered out.
- 3An unassigned task is stored as YOURS, not nobody's.
Quoted in the file: “we have all these employees, and when I go to create a new task in a project I can only assign it to me.” The comment names the cause: it read /api/users, 'which is Clerk-only AND admin-gated. Two consequences, both bad: a builder with twelve crew and six reps saw only the handful with logins, and a non-admin got a 403 and silently fell back to self-only — so the one person who most needs to hand work off couldn't.' The unassigned-means-mine rule closes the other half: 'Leaving it NULL is how tasks end up ownerless, which is the state the client reported seeing on every row.'
- Admin-gated user list blocking delegation
- Crew without logins invisible to the assigner
- NULL assignees producing ownerless tasks
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 →