> ## Documentation Index > Fetch the complete documentation index at: https://docs.chamelio.ai/llms.txt > Use this file to discover all available pages before exploring further. # Assigning Tasks in Flows: A Guide to Assign Strategy > Route flow tasks automatically with Round Robin, Group with Default, By Workload, and By Prompt Almost every step in a Chamelio flow eventually needs a person to do something — fill in a field, review a negotiation, sign a document, or approve content before it moves forward. Wherever a step needs a human in the loop, an assignment control determines who that person is. **Assign Strategy** lets you define a rule for how the assignee is picked, instead of hardcoding one person's name, and Chamelio applies that rule every time the flow runs. ## What "assigning" means in Chamelio Every flow run creates a task, and that task always has an assignee — the person currently responsible for the next action. As a flow moves through its steps, the assignee can change: whoever fills out a Collect form isn't necessarily who reviews the Negotiate step or signs the final document. Leaving a field Unassigned puts the task in a shared queue until someone claims it; setting a rule routes it automatically. ## The "Assign to…" menu Wherever you can assign a step, the same core menu opens (a couple of options only appear where they make sense): * **Unassigned** — leaves the task unowned until someone picks it up * **User Assign** — hardcodes one specific teammate as the owner * **Role based assignment** — routes by Owner (the task's overall owner) or Requester (whoever submitted the intake) * **From Flow** — pulls the assignee dynamically from an earlier variable * **Assign strategy** — opens the smart-routing rules below ## The four Assign Strategies | Strategy | How it works | | ------------------ | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | Round Robin | Cycles through a list of users or groups, handing each new task to the next person in line | | Group with Default | One default assignee normally handles the work; additional users act as a backup pool | | By Workload | Assigns to whoever in the selected pool currently has the lightest load | | By Prompt | Hands the decision to Chamelio's Agent — you write plain-language instructions (e.g. route by region or contract type) and the agent picks the assignee at runtime. Only available on step-level fields, not the workflow-wide default | ## Where you can use Assign Strategy | Location | Notes | | ------------------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | Workflow Settings (Ownership → Users) | Round Robin, Group with Default, and By Workload only — no By Prompt, since there's no context yet to reason about | | Collect | The "Assign to…" field for who receives and fills in the request | | Negotiate | The Review Assignee field — all four strategies apply, and **Add condition** lets you build rules like routing high-value contracts to one reviewer with a fallback Else assignee | | Sign | The Signatures coordinator field — all four strategies apply | | Approval | Each approver group under Select Approvers can use a strategy instead of naming people directly | | Agent (Human Approval) | The reviewer field uses the same menu, including all four strategies | | Customization | **Exception:** the Assignee attribute only supports a static Value or From Flow — Assign Strategy isn't available here | Reach for Round Robin when work is interchangeable and you want fair rotation. Use Group with Default when one person should usually own the work but needs a safety net. Choose By Workload when volume is uneven. Save By Prompt for cases where the right assignee genuinely depends on the content of the request.