Teams

Teams group the people in your company. They share the company's seat pool, they never have their own subscription, and putting somebody on another team never costs another seat.

What it does

The Teams page lists every team with its member count, how many of those members are team admins, how many hold a licensed seat, whether it is the default team, and your own role in it. Archived teams appear when you ask for them.

Create team takes a name and an optional description. Whoever creates a team becomes its team admin, so a team is never left with nobody to run it.

Open on a row gives you the team dialog:

• Rename the team.
• Set a default shared workspace path — the folder team members are told to open in the desktop app. This is a pointer, not storage; Roadmap Flow does not put anything there.
• Change any member's team role between team admin, editor and viewer.
• Remove somebody from the team. Their company seat is unchanged.
• Add a member from the people already in your company.
• Archive the team, or Restore it if it is already archived.

Archiving is deliberately narrow. It hides the team and stops it being used. It does not delete anyone's account, does not end anyone's company membership and does not release a single seat. Team membership rows survive, so restoring is lossless. The audit entry records that explicitly.

The default team cannot be archived. Point the default at another team on Company settings first.

When to use it

• Your company has more than one product area, squad or region.
• You want one person to run onboarding for their own group without giving them the whole company.
• A team disbanded and you want it out of the way without losing the record of who was in it.
• A team needs to be told which shared folder to open.

When not to use it

• As a permissions system for roadmap content. Roadmaps are files on people's computers; team membership does not lock or unlock a roadmap.
• As a project or sprint container. A team is a group of people, nothing more.
• To save money. Teams do not affect billing in any direction.

3-minute flow

1. Open Teams and click Create team.
2. Name it after the group, not the project — groups outlive projects.
3. Click Open on the new team.
4. Add members from the dropdown and give each one a team role.
5. Promote at least one person to Team admin so you are not the only route into it.
6. Paste the shared workspace path if the team uses one, and Save.

Best use cases

• A company of forty split into six squads, where each squad lead runs their own membership and nobody has to route requests through one administrator.
• Putting a principal PM on four teams so they see all four groups — still one seat.
• Archiving last year's programme team so the list stays readable, with the membership record intact for whoever asks in six months.

Common mistakes

• Creating one team per project. You will archive them constantly. Teams are people.
• Expecting a team admin to be able to invite new people into the company. They cannot — inviting is a company-level action. A team admin staffs their team from people who are already in the company.
• Archiving a team to remove somebody's access. It removes nothing. Suspend or remove them on People instead.
• Renaming a team to a name another team already uses. Roadmap Flow refuses it, including when you restore an archived team into a name that has since been taken.

Related guide pages

• Company, teams and seats
• Company and team roles
• People
• Team workspace coordination

Availability

Team. The company owner and company administrators see and administer every team. A team admin sees the teams they run or belong to, and administers only the ones they run.