Skip to main content
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. Team view

​
Team structure

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