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

# 3. Understand teams and Team Agents

> Learn the shared boundary for people, a Team Agent, workforce agents, channels, tools, and knowledge.

A team is the shared operating boundary for a group. It combines membership, access rules, a Team Agent, specialist workforce agents, channels, connectors, teamspace knowledge, activity, and usage.

<img src="https://mintcdn.com/superember/hET95aNwVbP7yQUV/images/onboarding/team-view.png?fit=max&auto=format&n=hET95aNwVbP7yQUV&q=85&s=b1d46dd1316119587d62828124463a9b" alt="Team overview" width="2560" height="300" data-path="images/onboarding/team-view.png" />

## Do this

Choose **Show me** in the mission banner. The walkthrough points to the **Agent** tab, then highlights the real Team Agent and reporting workforce card.

1. Open a team from **Your teams** in the sidebar.
2. Read its purpose and visibility.
3. Confirm the intended members and at least one lead.
4. Open **Agent** and identify the Team Agent at the root.
5. Inspect any indented workforce agents and their **Reports to** relationship.
6. Open **Channels** and identify the team's Main channel, if assigned.
7. Open **Emberbase** and confirm the teamspace is the team's section inside Company Emberbase.

## Team Agent versus workforce agents

```mermaid theme={null}
flowchart TB
    T[Team boundary]
    T --> M[Members and leads]
    T --> TA[Team Agent]
    T --> C[Channels and connectors]
    T --> E[Teamspace in Company Emberbase]
    TA --> A1[Workforce agent]
    TA --> A2[Workforce agent]
    A2 --> A3[Nested specialist]
```

* The **Team Agent** is the team's primary AI identity. Team channels and shared tools route through it.
* A **workforce agent** is a specialist beneath the Team Agent. It has a narrower purpose and receives work through the reporting hierarchy.
* A workforce agent may have its own direct reports, creating a deeper delegation tree.
* A **subteam** is an organizational child team. It is not the same as a workforce agent.

The product UI uses **workforce agent** for persistent specialists. “Subagent” is a useful generic term, but the reporting tree is the source of truth for which persistent agent can receive delegation.

## Understand the tabs

| Tab        | What it controls                                                       |
| ---------- | ---------------------------------------------------------------------- |
| Overview   | Team purpose, activity, capability policy, resources, and recent work. |
| Members    | Who belongs to the team and who leads it.                              |
| Agent      | The Team Agent and its reporting workforce.                            |
| Connectors | Applications authorized for this team surface.                         |
| Channels   | Channels routed to the Team Agent and the optional Main channel.       |
| Emberbase  | Team-scoped knowledge inside Company Emberbase.                        |
| Usage      | Activity and resource consumption attributed to the team.              |

## Visibility and access

* **Open** teams are discoverable and can be joined according to workspace policy.
* **Closed** teams remain visible, but membership is controlled.
* **Executive** is a protected closed coordination layer with stricter access and change rules.
* Channel assignment does not override team membership or Team Agent access.

## You are done when

The checklist marks **Understand a team** as done after the workspace has a team-bound surface or a collaborative team.

Continue with [Build the team workforce in Fleet](/onboarding/workspace).