Organizations are not flat. Your company has divisions, those divisions have teams, and those teams have sub-teams. But until today, Closot's teamspaces only went one level deep — forcing teams to either flatten their hierarchy into a single list or create workarounds with naming conventions and tags.
Starting today, you can create teamspaces within teamspaces, nesting as many levels deep as your organization requires. Your workspace hierarchy can finally match how your company actually works.
Why hierarchy matters
Consider a typical engineering organization. You have an Engineering teamspace at the top level. Beneath it sit Frontend, Backend, Mobile, and Infrastructure teams. Each of those might have further subdivisions — the Backend team has separate groups for API, Data Platform, and Auth. Before nested teamspaces, all of these existed at the same level in the sidebar, creating a wall of teamspaces that was difficult to navigate and impossible to manage permissions for coherently.
Nested teamspaces solve this by letting you model your actual org chart:
How permissions cascade
When you create a sub-teamspace, it inherits its parent's permissions by default. Everyone who can access Engineering can access Frontend, Backend, Mobile, and Infra. But you can override at any level — restrict the Auth sub-teamspace to only security engineers, or open the Mobile teamspace to your design partners who need visibility into platform-specific constraints.
This cascading model means you set permissions once at the top level and only make exceptions where they matter. No more managing access lists across dozens of independent teamspaces.
Each sub-teamspace is fully featured
A sub-teamspace is not a folder — it is a complete workspace environment. Each one gets its own boards with kanban and sprint views, its own wikis with verification workflows to keep documentation accurate, its own meeting notes with AI-generated summaries, and its own dashboards for tracking team-specific metrics.
The Frontend sub-teamspace might have a board tracking component library work with a kanban view. The Backend sub-teamspace uses sprint views with two-week cycles. The Infra team prefers a calendar view for maintenance windows. Each team works the way it wants, while the parent Engineering teamspace provides cross-cutting visibility through linked databases that pull from every child team.
Marketplace templates per team type
Setting up a new sub-teamspace is fast with Closot Marketplace templates. We have published starter templates for common team types — engineering squad, design team, marketing pod, customer support group — each pre-configured with the right boards, wiki structures, and automations. Apply a template when creating the sub-teamspace and your team starts with best-practice structure instead of a blank canvas.
Chat channel mapping
Each sub-teamspace can map to its own chat channel. The Engineering teamspace maps to #eng. Frontend maps to #eng-frontend. The Backend API sub-team maps to #eng-backend-api. Notifications, ticket updates, and Closot AI Agent interactions flow to the right channel automatically. When someone creates a ticket from chat, it lands in the correct sub-teamspace's board based on the channel it came from.
Universal search respects hierarchy
Universal search now understands nesting. Search from the Engineering teamspace and results include all child teamspaces. Search from Backend and results are scoped to Backend and its children (API, Data Platform, Auth). This makes finding information intuitive — the search scope matches where you are in the hierarchy.
How to get started
Navigate to any existing teamspace, open its settings, and click Create sub-teamspace. You can convert existing top-level teamspaces into children by dragging them in the sidebar, and all content, permissions, and integrations transfer automatically. There is no limit to nesting depth, though we recommend keeping hierarchies to three or four levels for navigability.
Nested teamspaces are available today on all plans. If you have been managing a growing organization with flat teamspaces and increasingly creative naming conventions, this update is for you.