Sub-teams
Open My Account → Sub-teams to nest teams under a parent so your org chart maps onto EKB. Each sub-team is a full team — its own members and admin view — that shares the family's license, credits, and seats rather than holding a separate pool.
Only team admins can open this tab and create or edit sub-teams.
The header explains how sharing works and shows seat usage across this team and its sub-teams. If your license limits how many teams you can create, the UI also shows how many of that limit are used.
Empty State
If there are no sub-teams yet, the page shows No sub-teams yet. Create one to get started. and + New sub-team.
Add a Sub-Team
Click New Sub-Team
The create form opens on the page.
Fill in the Fields
Field Description Name Sub-team name (for example Marketing)Credit cap Ceiling on credits this team and everything below it may draw. Toggle Uncapped (on by default) to leave it unbounded. Seats Ceiling on seats this team and its subtree may use. Toggle Uncapped (on by default) to leave it unbounded. Unused seats stay available to other teams. Allow this team to create its own sub-teams Off by default. When on, admins of this new team can create their own children. If this parent team has a Team SSO configuration, an extra option appears: Copy this team's SSO configuration to the new sub-team. The copy is independent (its own ACS URL and Entity ID). Later changes on the parent do not reach it.
Create
Click Create. Cancel closes the form without saving.
How the Tree Works
When at least one sub-team exists, the page shows an expandable tree:
| Column | Description |
|---|---|
| Name | Team name |
| Credit cap | Credit ceiling for that team and its subtree |
| Seats | Seat ceiling for that team and its subtree |
| Members | Member count |
| Sub-teams | Nested children |
| Host | Dedicated host/subdomain, if set |
| Sign-in policy | That team's own subdomain sign-in switches, when policy data is available |
| Active | Whether the team is active |
Each row has four actions: Domain (manage the host/subdomain), Sub-team (add a sub-team under it), Edit (name, caps, Allow, Active) and Delete (see Delete a Sub-Team).
Nesting Depth
Teams can nest up to 5 levels below the top-level (root) team.
Who Can Create Deeper Sub-Teams
- The root team can always create children.
- Creating a sub-team under another sub-team requires that parent to have Allow this team to create its own sub-teams enabled (off by default).
Seat Allocation (Shared License Pool)
Seats belong to the license family, not to a single team in isolation.
| Concept | Meaning |
|---|---|
| Seat allocation / seat cap | A ceiling on how many seats that team and its subtree may use |
| Not a reservation | Unused seats stay available to sibling teams |
| Distinct people | The same person on a parent and a child counts as one seat |
Inviting Members to a Child Team
Child-team invites draw from the parent license pool. If a child has no local seat cap of its own, invites are not blocked — seats come from the shared family pool (subject to ancestor ceilings).
If capacity is exhausted, ask a parent-team administrator to raise the seat allocation or free seats.
Credit Caps on Sub-Teams
A credit cap on a sub-team is a ceiling on how many credits that team and everything below it may draw from the shared credit pool in the billing period. Like seats, it does not reserve credits — unused headroom remains available to siblings.
For project-level ceilings, see Project credit allocation. For the subtree usage dashboard, see Credit Consumption.
Optional Host / Subdomain
Sub-teams can be given a dedicated host/subdomain (managed from the Sub-teams UI). That matters for Team SSO, which can offer a default IdP configuration on the team's subdomain.
Delete a Sub-Team
An admin of the sub-team's parent, or of any team above it, can delete it with the row's Delete action. Admins of the sub-team itself cannot delete it unless they also administer a team above it, and the top-level team cannot be deleted from here.
Deleting a sub-team cannot be undone. If you may need the team again, switch it to inactive with Edit → Active instead.
Click Delete on the Row
A confirmation window opens and lists everything the deletion will do, for that team as it is right now.
Review Each Consequence
Only the consequences that apply to this team are shown:
Consequence What happens Sub-teams move up Its own sub-teams move up one level, under its parent. They keep their own credit cap, seat allocation and Allow setting. The deleted team's own cap and seat allocation no longer apply to them, and its admins can no longer manage them through it. Members are removed Everyone loses access to the team and its pending invitations are cancelled. Anyone whose home team it was gets a new one: another team they belong to, otherwise a new personal team. Removed members receive an in-app notification. Projects are destroyed Every project in the team is permanently deleted with its knowledge base (files, vectors, knowledge graph), agents, chats and workflows. Members' personal default projects are not deleted; they follow their owner's new home team. Team settings are deleted Its subdomain is released, and its SSO configurations, branding, toolkit credentials, team skills and custom toolkits are deleted. A custom toolkit it shared with other teams stops working for them too. Credits return to the parent Its remaining credits are added to its parent, and its usage this period stays counted against the teams above it. Tick Every Box and Delete
Tick the box for each consequence, plus I understand this cannot be undone. Delete sub-team stays disabled until every box is ticked.
If the team changed while the window was open (someone added a project or a member, for example), the deletion is refused and the window reloads with the new list for you to review again.
Project Removal Progress
The team disappears from the tree immediately, and nobody can open its projects from that moment. Destroying the projects themselves runs in the background and can take a few minutes for large knowledge bases.
While it runs, Recently deleted below the tree shows how many projects have been removed. If removal fails, the entry shows the error and a Retry button. Deletions stay listed for 7 days.
Where Deletions Are Recorded
- Credit Consumption keeps showing the deleted team's usage, labelled (deleted).
- Credit transfers to or from the deleted team stay in the transfer history.
- The team audit log records the deletion on the parent team, and the move on each sub-team that moved up.
Who Can Manage Sub-Teams
| Role | Access |
|---|---|
| Team Admin (including admins inherited from an ancestor) | Create, edit and delete sub-teams in scope; set credit/seat caps; toggle Allow sub-teams; manage subdomain |
| Editor / Member | No Sub-teams tab |
Admin authority flows down the tree (parent can manage children), not sideways or up.