Introducing Sub Teams
Organize your company with nested team structures. Departments, squads, and working groups — finally represented properly.
Real organizations aren't flat. They have departments, teams within departments, and squads within teams. Komore now supports this with Sub Teams.
Nested team structure
- Parent and child teams: — Create teams within teams to match your actual org structure.
- Inherited access: — Child teams can inherit permissions from their parent, or override them.
- Team channels: — Each team automatically gets its own chat channel for focused communication.
- Team views: — Filter tasks, projects, and analytics by team to see only what's relevant.
How it works
Create a parent team like "Engineering," then add sub-teams like "Frontend," "Backend," and "DevOps." Assign employees to the most specific team — they automatically belong to parent teams too.
Better visibility
Managers can see across all their sub-teams. Team leads see their squad. Individual contributors see their immediate team. Everyone has the right level of visibility.
Sub Teams are available now for all workspaces.
Related reading
Continue with related posts to go deeper into practical workflows, product use cases, and implementation ideas.
All In One Workspace Software for Startups: What Actually Matters
A practical guide to choosing all in one workspace software for startups that need execution, communication, and knowledge in one system.
Why Teams Search for Project Management Software With Docs and Chat
Project management alone is not enough. Teams increasingly want tasks, docs, and chat in one product because work context breaks when those systems are separate.
What Operations Teams Need From an Internal Collaboration Platform
Operations teams need more than messaging. They need process visibility, documentation, reporting, and shared execution in one internal collaboration platform.