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

# Multi-Expert Delegation

> Have multiple Experts collaborate to tackle complex tasks

When an Expert encounters a subtask that falls outside its area of expertise, it can "delegate" that task to another Expert better suited for the job. This is multi-Expert delegation — different Experts collaborate like a team, each contributing their strengths.

## How It Works

<Steps>
  <Step title="Task Identification">
    You're chatting with an Expert. While working on your request, the Expert identifies a subtask that requires a different domain of expertise — for example, your full-stack Expert needs a data analysis Expert to handle a statistical task.
  </Step>

  <Step title="Automatic Delegation">
    The Expert automatically selects the right specialist and initiates the delegation. You'll see the process in the conversation, including which Expert was chosen and the specific task being delegated.
  </Step>

  <Step title="Subtask Execution">
    The delegated Expert takes over the task in the background, using its own Skills and tools to complete the work.
  </Step>

  <Step title="Result Return">
    Once the subtask is complete, the results are automatically returned to the primary Expert. The primary Expert integrates the results into the current conversation and continues advancing your task.
  </Step>
</Steps>

## Typical Scenarios

<CardGroup cols={2}>
  <Card title="Cross-Domain Collaboration" icon="handshake">
    Your coding Expert needs data visualization during development → delegates to a chart design Expert
  </Card>

  <Card title="Language Translation" icon="language">
    Your Chinese writing Expert needs to translate a technical document → delegates to a translation Expert
  </Card>

  <Card title="Professional Review" icon="magnifying-glass">
    Your frontend Expert has completed page development → delegates to a security Expert for a code security audit
  </Card>

  <Card title="Content Creation" icon="pen-fancy">
    Your technical Expert has written feature documentation → delegates to a marketing Expert to polish it into user-facing copy
  </Card>
</CardGroup>

## Delegation Transparency

The entire delegation process is **fully transparent** to you. You can clearly see in the conversation:

* **Delegation initiated**: Which Expert the primary Expert delegated to, along with the specific task description
* **Execution process**: The delegated Expert's work process (shown as a summary)
* **Results returned**: The subtask completion results and how the primary Expert integrates them

<Tip>
  Delegation is the Expert's autonomous decision. You don't need to manually specify "hand this task to a certain Expert" — the primary Expert automatically determines whether delegation is needed and which Expert to delegate to based on the nature of the task.
</Tip>

## Delegation Hierarchy

To ensure conversation security and controllability, delegation follows a layered tool permission mechanism:

* **Primary Expert (L1)**: Has full tool permissions, including core capabilities like plan creation and delegation scheduling
* **Delegated Expert (L2)**: Has tool permissions needed for the subtask, but certain core management capabilities are reserved for the primary Expert

This means a delegated Expert cannot further delegate tasks to a third Expert, nor can it modify the primary conversation's plan document.

<Note>
  Conversation content and tool calls generated by delegation also consume your credits. Exact consumption is shown in real time within the product.
</Note>

## Delegatable Experts

The range of Experts available for delegation depends on:

* **Experts you've used**: Experts you've previously chatted with can be delegated to
* **Publicly listed Experts**: Published Experts on the marketplace can also be delegated to

<Warning>
  Delegation requires the target Expert to have relevant expertise. If no suitable delegation target is available, the primary Expert will attempt to handle the task itself or inform you of the current limitations.
</Warning>

## Delegation Authorization Settings

You can manage delegation behavior in your personalization settings:

* **Allow delegation**: A global toggle controlling whether Experts can initiate delegation
* **Target allowlist**: Specify which Experts can be delegated to

See the delegation authorization section in [Personalization Settings](/en/documentation/memory/personalization).

## FAQ

<AccordionGroup>
  <Accordion title="Does delegation affect the main conversation's context?">
    No. Delegation is executed in an isolated context. The delegated Expert only sees the subtask description passed by the primary Expert — it cannot access your full conversation history. Once the subtask is complete, results are returned to the main conversation as a summary.
  </Accordion>

  <Accordion title="Can I prevent Expert from auto-delegating?">
    Yes. You can disable delegation in your personalization settings. When disabled, the Expert won't initiate any delegation and will handle all tasks itself.
  </Accordion>

  <Accordion title="What happens if a delegated subtask fails?">
    The primary Expert receives failure feedback and attempts an alternative approach — it may handle the subtask itself, or inform you of the issue and ask for your guidance.
  </Accordion>

  <Accordion title="Does delegation use the delegated Expert's memory?">
    The delegated Expert can access its own memory and Skills when executing the subtask. This is precisely the value of delegation — leveraging its specialized expertise and accumulated knowledge.
  </Accordion>
</AccordionGroup>