Members & assignment
A shared project adds two things on top of a normal one: a way to manage members, and a way to assign tasks to people.
Members
Section titled “Members”The members view lists everyone on the project. The owner can remove a member, and any member can use Leave Project to remove themselves.
When someone is removed or leaves, their tasks in that project are archived for them, with a history note explaining why, so nothing silently vanishes. The owner’s own project is never archived by this.
Assigning tasks
Section titled “Assigning tasks”Each task can be assigned to one member, or left unassigned:
- Claim an unassigned task for yourself with
M(on iOS, swipe a row in the Unassigned pool). - Assign to anyone with
G, or from the task’s row or context menu, choosing yourself, another member, or Unassigned.
Where assigned tasks live
Section titled “Where assigned tasks live”Assignment decides where a task shows up:
- Assigned to you: it appears in your own Inbox, Today, or Backlog, like any other task.
- Assigned to someone else: it stays visible in the project view but leaves your personal sections.
- Unassigned: it sits in the project’s shared Unassigned pool, where anyone can claim it.
Only the assignee can complete a task; an unassigned task can be completed by anyone. The project view labels each task with its assignee, so it is always clear who has what.
How new tasks are assigned
Section titled “How new tasks are assigned”- Created from inside a shared project view: it goes to the Unassigned pool.
- Created with
#TheProjector via the picker: it is assigned to you and lands in your Inbox.
This keeps the common cases intuitive: work you file for yourself stays yours, and work you drop into the shared space stays open for anyone to take.