Every team carries a colour, a company and a mission, with live counts of open tasks, overdue work and hours logged for the whole team and each person in it. Members get a team role, Lead, Editor, Contributor, Viewer or Member, that sits alongside their organisation role rather than replacing it.
Included on every plan, free included
Give a team a name, a colour, a department and a mission, and set which company it belongs to if you run more than one. Archive a team from its status field when the work is done, rather than deleting the record.
Add a person and give them a team role, Lead, Editor, Contributor, Viewer or Member, which controls what they can manage on this team specifically. It never grants more than their organisation role already allows; a Lead cannot use it to reach a page their own access blocks.
Assign projects to a team from a simple search, and that becomes the team’s work for every metric on its page, active project count, open and overdue tasks, and completion rate, all computed live rather than typed in.
Every member gets a bar showing their open tasks next to the busiest person on the team, plus hours logged and how many of their open tasks are already late. Click through to a person’s own page for an eight-week view of the hours they have actually logged.
Each member’s five nearest open tasks show on their own Personal priorities panel, overdue ones first, so a manager can see who needs help without opening every task themselves.
The part you would otherwise find out in week three. If one of these is central to how you work, raise it before you buy rather than after.
It shows open task counts and hours logged per person, side by side, so an imbalance is visible at a glance. It does not plan capacity or warn you before someone is over-allocated; that judgement is still yours.
No. A team role such as Lead or Editor only ever works within what that person’s organisation role already permits. It organises who manages the team; it cannot widen access.
They can be. Their open tasks and logged hours count toward every team they belong to, so a shared person is not split fractionally between teams; each one sees the full picture of that person’s work.
Not a dedicated one. Conversation in WorkBOS happens in the org-wide channel, a project’s own channel, or a direct message; Teams itself is about who is on the roster and what they are carrying.
The full product documentation for this module is at /docs/teams.
Free for up to 5 seats, no card required. Every module is in the same workspace, so nothing needs connecting to anything.