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

# Delegate in Slack

> Give SuperEmber clear work, choose ask or delegate, and follow governed operation threads.

Slack is the fastest daily work surface for SuperEmber. Use the channel where the context already lives and mention the app explicitly.

## Start with the deliverable

```text theme={null}
@SuperEmber draft a customer update from this thread. Include the root cause, owner, and next checkpoint. Keep it under 150 words.
```

Name the output, source context, constraints, deadline, and whether the agent may act or should only draft.

## Choose the right identity

* Use **Company AI** for general organization requests and unassigned channels.
* Use a **Team Agent** for work that belongs to one team's members, tools, and teamspace.
* Use your **Personal Agent** for private context and personal accounts.

## Ask another agent

Use **ask** when you need a read-only answer from another team's context:

```text theme={null}
@SuperEmber ask the support specialist for the current incident status and return a concise answer here.
```

The target answers without accepting a task handoff.

## Delegate a task

Use **delegate** for bounded execution:

```text theme={null}
@SuperEmber delegate this to the research specialist: compare the three options in this thread, cite the evidence, and return a recommendation. Do not make external changes.
```

Delegation follows the Fleet reporting hierarchy. The target Team Agent or specialist must be eligible and active.

## Follow the operation

When the target team has a Main channel:

1. SuperEmber creates an operation thread there.
2. The root shows who is taking the task and its status.
3. The specialist posts work and review requests in that thread.
4. The final result returns to the original thread.

If there is no Main channel, SuperEmber can use a headless fallback for ordinary delegation. A human escalation cannot silently execute; the source is told that the team could not be notified.

## Understand review

Every boundary-crossing action is reviewed against the user's intent and risk. Automatic review can approve, deny, or park the exact call for a human.

A delegated request is not direct human authorization for destructive, permission-changing, financial, legal, credential-sensitive, or other high-impact actions.

When a human is required, review the exact action in the target operation thread. Approval resumes that call once. Denial causes the specialist to choose a safer route or report the blocker.

## Ask for a workflow

When the process should repeat:

```text theme={null}
@SuperEmber turn this into a weekly workflow: pull the metrics, summarize changes, ask for approval, then post the update.
```

## Avoid ambiguous handoffs

Weak:

```text theme={null}
@SuperEmber handle this.
```

Better:

```text theme={null}
@SuperEmber identify the owner for each open item, draft a follow-up, and wait for my approval before posting anything externally.
```

## Related pages

* [Teams and Team Agents](/product/teams-and-team-agents)
* [Automatic review and escalations](/product/auto-review-and-escalations)
* [Slash commands](/reference/slash-commands)