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

# Manage a fleet

> Create, configure, and provision specialist agents.

Fleet lets you build and inspect the persistent AI workforce for each team.

The Fleet surface is labeled **Preview** while its interaction model evolves. Its stored Team Agents, workforce agents, and reporting relationships are operational.

## Create A Specialist Agent

1. Open **Dashboard > Fleet**.
2. Choose **New agent**.
3. Add a name.
4. Add a title.
5. Write a purpose.
6. Save.

The purpose is important. It tells teammates and other agents when this specialist should receive work.

## Inspect And Configure An Agent

Select an agent on the Fleet canvas to open its inspector. The inspector keeps the canvas available while you review:

* **Setup** for purpose, model, channels, capabilities, and reporting lines
* **Activity** for recent runs, failures, and handoffs
* **Chats** for recent agent conversations

Confirm the agent's parent, direct reports, and team boundary before changing its configuration.

Choose **Configure agent** to expand the inspector into the full configuration window. Closing the window returns to the inspector without losing your place.

The full editor separates the agent's configuration into Identity, Role & instructions, Model, Capabilities, Team & delegation, Knowledge & memory, Channels, and Advanced.

## Write The Operating Brief

Use **Role & instructions** for the specialist's job brief, optional communication style, and operational boundaries. These values are used when a new agent session starts; they do not rewrite a session that is already running.

Platform security, connector approvals, and tool restrictions always remain higher priority than the operating brief.

## Write A Useful Purpose

Weak:

```text theme={null}
Helps with marketing.
```

Better:

```text theme={null}
Researches campaign performance, identifies conversion issues, prepares weekly growth summaries, and drafts experiment briefs.
```

## Choose Workspace Source

Open **Advanced** to choose how a specialist starts:

| Source           | Use it when                                                     |
| ---------------- | --------------------------------------------------------------- |
| Own workspace    | The specialist should have separate files, notes, and outputs.  |
| Parent workspace | The specialist should inherit the parent context and work area. |

## Provision The Agent

Draft agents are not live. Click **Provision** when the profile is ready.

Provisioning creates the runtime needed for the specialist to work. If provisioning fails, retry after checking limits and required setup.

## Arrange The Fleet

Use fleet relationships to show how work should move:

* the Team Agent at the root of each team workforce
* specialists beneath the agents that coordinate them
* reviewer agents near the work they synthesize

Moving a workforce agent changes its operational delegation parent. Confirm the destination team, access, connectors, and teamspace before saving the change.

## Use Fleet Agents In Workflows

For direct work, delegation follows the persistent parent-child edges shown in Fleet and uses a team Main operation thread when available. In workflows, prefer explicit fleet or collaboration nodes. That keeps child work, join rules, output schemas, and reviewer synthesis visible in run history.