> ## 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.

# Teams and Team Agents

> Understand team boundaries, Team Agents, workforce agents, channels, tools, access, and teamspace knowledge.

A SuperEmber team combines the people and AI workforce responsible for one area of the company.

The team is the boundary for membership, leadership, a Team Agent, persistent workforce agents, channels, connectors, teamspace knowledge, activity, and usage attribution.

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

## Team structure

```mermaid theme={null}
flowchart TB
    O[Organization]
    O --> CA[Company AI]
    O --> EX[Executive AI]
    EX --> TA1[Team Agent: Product]
    EX --> TA2[Team Agent: Support]
    TA1 --> W1[Research specialist]
    TA1 --> W2[Delivery specialist]
    W2 --> W3[Nested specialist]
```

| Part             | Responsibility                                                         |
| ---------------- | ---------------------------------------------------------------------- |
| Members          | People allowed to see and use team resources.                          |
| Leads            | People allowed to manage membership and team resources.                |
| Team Agent       | Primary shared AI identity for the team.                               |
| Workforce agents | Persistent specialists that report through the team's agent hierarchy. |
| Channels         | Team conversation surfaces routed to the Team Agent.                   |
| Main channel     | Operation surface for delegated work and human escalation.             |
| Connectors       | Shared applications authorized for the Team Agent.                     |
| Teamspace        | The team's section inside Company Emberbase.                           |

## Team Agent

Every team has one Team Agent at the root of its workforce. It represents the team in channels, owns the team's connected capabilities, and decides when an eligible specialist should receive work.

The Team Agent is not a Personal Agent. Its context and tools serve the team, and access follows team membership and policy.

## Workforce agents

Workforce agents are persistent specialists beneath a Team Agent. The Fleet reporting tree determines which agent can delegate directly to which specialist.

A workforce agent can have its own direct reports, but moving an agent in Fleet changes the operational hierarchy—not only the diagram.

The UI uses **workforce agent** for these persistent specialists. “Subagent” is a broader technical term and may also describe temporary child work inside a workflow. Use the Fleet hierarchy when you need to know the persistent reporting relationship.

## Company AI and Executive AI

* **Company AI** is the organization-wide general entry point and fallback for channels without a Team Agent assignment.
* **Executive AI** is the protected coordination root across Team Agents. It has stricter access and mutation controls and should not be treated as a general team bot.

## Open and closed teams

* **Open:** discoverable and joinable according to workspace policy.
* **Closed:** visible, but membership is controlled.
* **Executive:** protected closed coordination team with additional guardrails.

Channel assignment never bypasses membership or agent-access checks.

## Related pages

* [Build the team workforce](/onboarding/workspace)
* [Fleets](/product/fleets)
* [Delegate in Slack](/guides/delegate-in-slack)
* [Automatic review and escalations](/product/auto-review-and-escalations)