Teams and org structure

What teams are for

Above a certain headcount, a flat member list stops being useful. Teams in ProMan are groupings of members — typically by department, discipline, or project pod. Teams show up in reports, can be @-mentioned, and can be given bulk access to projects.

Teams are available on Plus and above. Free plans can still group people via tags on their profile, but without the reporting rollup.

Creating a team

Go to Settings → Teams → New team. Pick a name ("Platform engineering", "Accounting", "Site Ops — Dubai") and an optional color. Add members by picking from the org roster.

You can nest teams one level deep (for example, "Engineering" → "iOS" and "Android"). Reports roll up automatically through the hierarchy.

Granting project access by team

On any project’s Members tab, you can add a whole team instead of picking members individually. Everyone on the team gets the project-level role you pick (Manager, Member, or Viewer), and any changes to the team flow through: add someone to the "Platform" team and they automatically get access to every project that team’s on.

Removing a team from a project removes the team-granted access, but doesn’t affect people who were also added individually.

Team-scoped reports

When you open Reports → Workload, a Team filter lets you see hours, task counts, and velocity per team. This is how most leads catch a team that’s quietly overloaded three weeks before it becomes a crisis.

Team mentions

Type @TeamName in any comment, description, or update to ping the whole team. Pings go out in-app; email digests combine multiple pings within an hour to avoid blasting people.

Team leads

Each team can have a Team lead — purely a label, no extra permissions. Team leads show up with a badge in the member list and on reports. It’s useful for anyone reading the workspace who needs to know who to ask.

Reorganizing

As the org changes, teams change. Reorganizing in ProMan:

1. Rename a team any time. All references update automatically.
2. Merge two teams by moving members and then deleting the empty team.
3. Split a team by creating a second team and moving members across.
4. Archive a team you’re not using but don’t want to delete — archived teams keep their history for reports but don’t show up in pickers.

Limits

Seat counts are per-organization, not per-team. Teams are a grouping concept — they don’t consume extra seats.

Next up

Internal collaboration is handled. Last chapter: client dashboards and public sharing.