> ## Documentation Index
> Fetch the complete documentation index at: https://ai-kb.automationanywhere.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Sub-teams

> Nest teams under a shared license, allocate seats, and set credit ceilings

Team admins can nest **sub-teams** under a parent team 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.

Open **My Account → Sub-teams**.

> Each sub-team has its own members and admin view, and shares this team's credits and seats. Set a credit cap or a seat allocation to bound how much of each pool a team and everything below it may draw; unused seats stay available to the other teams.

## How the tree works

* Browse an **expandable tree** of teams under your current team.
* Create a **New sub-team** under a chosen parent.
* Columns typically include name, credit cap, seats, members, nested sub-teams, host/subdomain, and active status.
* The header 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.

### 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](/project-settings/billing#project-credit-allocation).\
For the subtree usage dashboard, see [Credit Consumption](/my-account/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](/my-account/team-sso), which can offer a default IdP configuration on the team's subdomain.

## Who can manage Sub-teams

| Role                                                         | Access                                                                                             |
| ------------------------------------------------------------ | -------------------------------------------------------------------------------------------------- |
| **Team Admin** (including admins inherited from an ancestor) | Create and edit 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.

## Related

* [Credit Consumption](/my-account/credit-consumption)
* [Members](/my-account/team-members)
* [Team SSO](/my-account/team-sso)
* [Credits](/general/credits)
* [Cloud Licensing](/offerings/cloud/licensing)