The project team
The Team tab is about people rather than work. It answers who is on this project, what each of them can do, and whether the commitments already made to them add up to something a human can actually deliver.
Membership is explicit​
A project's teamProject teamThe explicit list of resources on a project, maintained on its Team tab with their skills and an allocation heatmap. Membership is declared, not inferred from who has appointments. is a list you maintain, not something inferred from who happens to have appointments.
That distinction does more than it looks. It means somebody can be on the team before any work is assigned to them, which is what makes this tab useful for planning rather than only for reporting: you can staff a project and then plan it, instead of discovering the team by looking at what was already planned.
Add and remove members from the tab. Membership is per project, so the same resourceResourceAn entity that can carry out work - a person, vehicle, tool, or room - that you schedule on the planning board. can be on several.
Skills and attributes​
Each member is listed with the skillsSkillA qualification a resource holds and a task can require, typically modeled as a filter group. Skills drive resource filtering, the project team view and the solver’s choice of who can do what. and attributes recorded against them, so you can see what the team collectively brings and where it is thin. A member with nothing recorded shows as having no skills, which usually means the attributes were never set on the resource rather than that the person cannot do anything.
This is the view to use when a project needs a capability nobody on it has. It is faster than opening resources one at a time to find out.
Allocation​
A heatmap shows planned hours per period across the team, drawn relative to the busiest member: the darker the cell, the more planned time. It is deliberately relative rather than absolute, because the question it answers is "is this evenly spread", not "how many hours exactly".
That makes two failure modes visible quickly:
- Somebody is over-allocated. More has been committed to them than they can deliver, so something on their plate will slip, and it may not be this project.
- Somebody is not planned at all. They are on the team but carrying nothing, which is either a staffing mistake or a sign that the plan is thinner than the team suggests.
The tab summarizes both: whether everyone is planned, and whether anybody is over-allocated.