Teams in Leanmote are how users get grouped for dashboards, Views, and metric rollups. Every metric on every dashboard can be filtered by team, so the team structure here directly affects how readable your dashboards are.
Create a team
Open
Administration → Teams.Click Create team.
Enter a team name. Match the name your engineering org uses internally — "Platform" not "Platform-Eng-2026".
Add members from the user list.
Click Save.
What a team configuration affects
Filtering dashboards by team.
Per-team Views (e.g., "Platform — Weekly").
Per-team rollups in Strategic Overview and Project Financials.
Activity distribution and review metrics on the Team Collaboration Network.
Nested teams
Some organizations group teams into divisions or pillars. Where supported, Leanmote represents this with nested team membership — a user can belong to "Backend Platform" which itself is part of "Platform". Roll-up metrics aggregate up the hierarchy.
Member transitions
When a teammate moves teams, change their team assignment as the move happens. Historical metrics remain attributed to whichever team they belonged to during the period in question — Leanmote does not retroactively rewrite team membership.
Common issues
Empty teams — teams with no members appear in filter lists but produce empty data. Either populate them or remove.
Cross-team contributors — for engineers who legitimately work across teams, choose the team that best reflects their primary affiliation. Cross-team work is captured in collaboration metrics regardless.
Related articles
Users management
Roles and access levels
What is a View?