Guide
Teams
Group members into teams like Drawing or Production, then assign a whole team to a deliverable or a project in one move.
Before you start
- Creating teams and editing rosters needs the Manage teams permission (Admin by default).
- Assigning a team to a deliverable needs Assign teams (Admin and Manager by default).
- Find team management under Settings, in Teams.
Create a team and build its roster
Create the team
Go to Settings, then Teams, and click New team. Give it a name and a color; the color carries through to the team chip everywhere it appears.
Add members
Click Members on the team row and tick people in or out. A member can be on any number of teams.
Decide about existing assignments
If the team is already assigned somewhere, changing its roster never touches those assignments by itself. When you close the member list, WorkWiser asks whether to update them now; choose Not now and nothing changes, and you can run Sync assignments from the team menu whenever you are ready.
Assign a team
On a deliverable
Open the assignee picker on any deliverable, or the assignee box in the bulk editor, and you will find a Teams group above the people. Ticking a team assigns it and brings its current members along; every member shows up as usual on boards, filters, and notifications. People the team covers are marked with a via hint in both pickers, so team coverage is easy to tell apart from someone you ticked individually.
On a project
On the project Team tab, Add team puts the whole roster on the project member list in one step. Removing the team later takes out the people it brought; anyone added individually stays.
Individuals stay individual
Adding someone by hand, on top of or instead of a team, marks them as individually assigned. Team changes and Sync never remove an individually-assigned person.
How team assignment behaves
The chip plus the people
Assigning a team puts a team chip on the deliverable and adds each current member. The chip is the durable fact; the members are its expansion, so everything that reads assignees keeps working.
Roster changes are explicit
New teammate joins the team? Existing assignments update only when you say so, either from the prompt after a roster edit or with Sync assignments on the team. The confirm always tells you how many deliverables and projects it touches.
Shared members survive
If someone is on two assigned teams, unassigning one team keeps them, because the other team still covers them.
Archive vs delete
Archive retires a team: nothing new can use it, everything it is already on stays, and you can restore it. Delete removes the team and its chips everywhere; the people it added stay behind as individuals.
Good to know
On a restricted project, assigning a team whose members are not on the project warns you that they cannot see it yet, and offers to add the team to the project in the same step.
Deactivated members are skipped automatically: they are never materialized onto assignments, and Sync treats them as having left the team.
Archived projects are read-only, so team operations skip them; a Sync simply leaves those assignments as they are.
Ready to see it on your own work?
WorkWiser is in early access. Tell us where to reach you and we will send an invite when it is your turn.